[meta-ti] Merging in linux-stable updates, git send-email

[Maupin, Chase]

> -----Original Message-----
> From: Denys Dmytriyenko [mailto:denis at denix.org]
> Sent: Friday, February 10, 2012 10:28 AM
> To: Maupin, Chase
> Cc: Koen Kooi; meta-ti at yoctoproject.org
> Subject: Re: [meta-ti] Merging in linux-stable updates, git send-
> email
> 
> On Fri, Feb 10, 2012 at 04:18:28PM +0000, Maupin, Chase wrote:
> >
> > > -----Original Message-----
> > > From: Koen Kooi [mailto:koen at dominion.thruhere.net]
> > > Sent: Friday, February 10, 2012 10:15 AM
> > > To: Maupin, Chase
> > > Cc: meta-ti at yoctoproject.org
> > > Subject: Re: [meta-ti] Merging in linux-stable updates, git
> send-
> > > email
> > >
> > >
> > > Op 10 feb. 2012, om 17:05 heeft Maupin, Chase het volgende
> > > geschreven:
> > >
> > > > So you changed the recipe name to use 3.2.5 for the PV.  But
> when
> > > I set the DISTRO_FEATURES to include tipspkernel I don't get
> all
> > > the patches you added to update to 3.2.5.  So can you maybe do
> a
> > > logic similar to how the patches are handled to set the PV
> based on
> > > whether tipspkernel is set in DISTRO_FEATURES?
> > >
> > > I have updated the patch locally to keep PV at 3.2. I can live
> with
> > > PV being "wrong" for the patched kernel till we figure out the
> > > python magic. Using gitpkgv would get us around all this, but
> > > that's a story for another day :)
> >
> > So for this recipe would the following line of code not work?
> >
> > PV = "${@base_contains('DISTRO_FEATURES', 'tipspkernel', "${PV}",
> "3.2.5", d)}"
> 
> You'll have a circular resolution in there, basically doing PV =
> ${PV}
> 
> You'd want to use := instead. But anyway, it seems heavy handed for
> the
> purpose...

Well, as long as we use the PSP version as the base I'm OK, which is what I think Koen is saying.

> 
> --
> Denys
> 
> 
> > Then leave the recipe as linux-ti33x-psp_3.2.bb but your PV
> should be
> > correct for your kernel right?