[meta-intel] [Patch v2 0/1] use bsp specific topic branch for sys940x BSP

Kamble, Nitin A nitin.a.kamble at intel.com
Thu Feb 28 16:18:29 PST 2013



> -----Original Message-----
> From: Bruce Ashfield [mailto:bruce.ashfield at windriver.com]
> Sent: Thursday, February 28, 2013 4:16 PM
> To: Kamble, Nitin A
> Cc: Zanussi, Tom; Hart, Darren; meta-intel at yoctoproject.org
> Subject: Re: [Patch v2 0/1] use bsp specific topic branch for sys940x BSP
> 
> On 13-02-28 6:34 PM, Kamble, Nitin A wrote:
> >
> >
> >> -----Original Message-----
> >> From: Bruce Ashfield [mailto:bruce.ashfield at windriver.com]
> >> Sent: Thursday, February 28, 2013 12:53 PM
> >> To: Kamble, Nitin A
> >> Cc: Zanussi, Tom; Hart, Darren; meta-intel at yoctoproject.org
> >> Subject: Re: [Patch v2 0/1] use bsp specific topic branch for sys940x
> >> BSP
> >>
> >> On 13-02-28 03:44 PM, nitin.a.kamble at intel.com wrote:
> >>> From: Nitin A Kamble<nitin.a.kamble at intel.com>
> >>>
> >>> Instead of pointing to the standard/base branch this commit points
> >>> to the standard/sys940x branch for the BSP kernel. There is no
> >>> functional change here as both branches are pointing to the same
> commit now.
> >>
> >> FYI: the dev kernel is going to switch to the 3.8 kernel's meta data
> >> shortly and then update to 3.9.
> >>
> >> So for any change like this, check against the 3.8 kernel as well.
> >> Since it should go there first, and I'll prop it to the dev kernel after.
> >>
> >
> > Bruce,
> >    These dev kernel recipes are valid in either case because they have
> > the working SRCREVs in them. So I don't see any reason to hold them off.
> >    And the v3.8 kernel bbappends work is following next. These dev
> > kernel bbappends are ahead because the dev kernel recipe is already in
> > the oecore, and the v3.8 kernel recipe is yet to make in to the oecore layer.
> 
> Right. All I'm commenting on is that while the -dev and 3.8 tree are both in
> sync, if you are changing something in dev .. make sure to check 3.8 and get
> me to merge it there at the same time (if it needs merging).

Ok, I am not pushing anything to the kernel repos, after the emgd branch & meta change which you already merged.
If anything new comes up I will push it to v3.8 repo too.

Nitin

> 
> Cheers,
> 
> Bruce
> 
> >
> > Nitin
> >
> >> Bruce
> >>
> >>>
> >>> Nitin
> >>>
> >>>
> >>> The following changes since commit
> >> 6281f14aee87d49a77a2f97df30f5107e613f06a:
> >>>
> >>>     crownbay: linux-yocto-dev recipe extension (2013-02-28 12:39:23
> >>> -0800)
> >>>
> >>> are available in the git repository at:
> >>>     git://git.yoctoproject.org/meta-intel-contrib nitin/misc
> >>>
> >>> http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin
> >>> /m
> >>> isc
> >>>
> >>> Nitin A Kamble (1):
> >>>     sys940x: linux-yocto-dev recipe extension
> >>>
> >>>    .../recipes-kernel/linux/linux-yocto-dev.bbappend  |   22
> >> ++++++++++++++++++++
> >>>    1 files changed, 22 insertions(+), 0 deletions(-)
> >>>    create mode 100644
> >>> meta-sys940x/recipes-kernel/linux/linux-yocto-dev.bbappend
> >>>
> >




More information about the meta-intel mailing list