[meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14: update meta branch SRCREV

[Wu, Chia Chuan]

> -----Original Message-----
> From: Wu, Chia Chuan
> Sent: Wednesday, August 12, 2015 9:26 AM
> To: Darren Hart <dvhart at linux.intel.com>
> Cc: meta-intel at yoctoproject.org
> Subject: RE: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14: update
> meta branch SRCREV
> 
> 
> 
> > -----Original Message-----
> > From: Darren Hart [mailto:dvhart at linux.intel.com]
> > Sent: Wednesday, August 12, 2015 12:42 AM
> > To: Wu, Chia Chuan <chia.chuan.wu at intel.com>
> > Cc: meta-intel at yoctoproject.org
> > Subject: Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14:
> > update meta branch SRCREV
> >
> >
> >
> > On 8/11/15 12:56 AM, Wu, Chia Chuan wrote:
> > >
> > >
> > >> -----Original Message-----
> > >> From: Darren Hart [mailto:dvhart at linux.intel.com]
> > >> Sent: Thursday, August 6, 2015 7:17 AM
> > >> To: Wu, Chia Chuan <chia.chuan.wu at intel.com>
> > >> Cc: meta-intel at yoctoproject.org
> > >> Subject: Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14:
> > >> update meta branch SRCREV
> > >>
> > >> On 8/3/15 3:03 AM, chia.chuan.wu at intel.com wrote:
> > >>> From: Wu Chia Chuan <chia.chuan.wu at intel.com>
> > >>>
> > >>> Enable i40e network driver for Intel Ethernet Controller
> > >>> XL710/X710 on Intel common BSP so that the NIC card is
> > >>> discoverable under River Forest
> > >> platform.
> > >>>
> > >>
> > >> This fails to apply to master, and we don't apply patches to fido
> > >> that haven't been first applied to master.
> > >>
> > >> Please develop against master and request backports to the stable
> branches.
> > > Darren, linux-yocto meta branch was separated out in master branch
> > > and pointing to " yocto-kernel-cache" repo. Fido branch still use
> > > the meta branch from "linux-yocto-3.xx" repo, the revisions would
> > > not be common for
> > the two branches.
> > >
> > > This patch is required for River Forest BSP ,which is
> > > developed/tested under
> > fido branch.
> >
> > Right you are. Thanks for pointing that out.
> >
> > This kind of justification should be included in the commit message
> > for any patch that cannot be applied to master first as it is a special case.
> Darren, sure, I should include this information at the beginning of the cover
> letter  & commit message. Thanks!
Darren, should I resend the patch by including the justification ?

> >
> > --
> > Darren Hart
> > Intel Open Source Technology Center