[PATCH V2] dtc: Implement -d option to write out a dependency file

[Stephen Warren]

David Gibson wrote at Thursday, January 12, 2012 4:12 PM:
> On Thu, Jan 12, 2012 at 07:24:04AM -0600, Jon Loeliger wrote:
> > > On Wed, Jan 11, 2012 at 08:29:58AM -0600, Jon Loeliger wrote:
> > > > > On Tue, Jan 10, 2012 at 10:12:48AM -0700, Stephen Warren wrote:
> > > > > > This will allow callers to rebuild .dtb files when any of the /include/d
> > > > > > .dtsi files are modified, not just the top-level .dts file.
> > > > > >
> > > > > > Signed-off-by: Stephen Warren <swarren at nvidia.com>
> > > > >
> > > > > Nice.
> > > > >
> > > > > Acked-by: David Gibson <david at gibson.dropbear.id.au>
> > > > >
> > > > > Jon, please apply.
> > > >
> > > > Will do with a patch for the DTC repo.
> > >
> > > Uh.. this patch is for the dtc repo, he sent it in addition to the one
> > > against the kernel version.
> >
> > I did not receive this patch for the DTC repo.
> > I have this patch for the kernel only on the arm list.
> >
> > I'm not saying he didn't do the worl, nor am I saying he
> > didn't post such a past.  I'm saying *I* don't have it!
> 
> Um.. so, the mail I was replying to you above, was for the dtc repo
> and you were on the recipient list.  Given the frequency with which I
> need to resend my own patches, I'm beginning to wonder if your mail
> system is dropping things, Jon..

In this case, it was my fault.

Jon's email system validates SPF and doesn't accept messages where that
fails. I was sending my patch through my personal email server but using
NVIDIA's email address, hence this failed the SPF check. I think I wasn't
notified of this because the bounce message my server would have
presumably generated probably experienced some similar issue getting back
to my NVIDIA email account.

I've reconfigured git to send email through NVIDIA's servers, although
now that means I have to be on the VPN to send patches:-(

-- 
nvpublic