* [PATCH 0/1] linux-yocto: 3.4 kernel updates
@ 2012-09-10 18:11 Bruce Ashfield
2012-09-10 18:11 ` [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates Bruce Ashfield
` (2 more replies)
0 siblings, 3 replies; 17+ messages in thread
From: Bruce Ashfield @ 2012-09-10 18:11 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Richard/Saul,
Here's a small bump to 3.4.10 (32 commits) and an update to
pickup some configuration changes from TomZ (no impact on existing
features). All in all, it's a nice set of small fixes, with no risk.
Cheers,
Bruce
cc: Tom Zanussi <tom.zanussi@intel.com>
The following changes since commit 21816355c00eadb2273d61b456f06239ca300b47:
bitbake: cooker: fix handling of exceptions during exception handling (2012-09-10 13:14:08 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (1):
linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++++----
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 ++++++++--------
2 files changed, 12 insertions(+), 12 deletions(-)
--
1.7.5.4
^ permalink raw reply [flat|nested] 17+ messages in thread* [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates 2012-09-10 18:11 [PATCH 0/1] linux-yocto: 3.4 kernel updates Bruce Ashfield @ 2012-09-10 18:11 ` Bruce Ashfield 2012-09-11 4:50 ` Khem Raj 2012-09-11 6:59 ` Martin Jansa 2012-09-10 18:14 ` [PATCH 0/1] linux-yocto: 3.4 kernel updates Bruce Ashfield 2012-09-12 17:26 ` Saul Wold 2 siblings, 2 replies; 17+ messages in thread From: Bruce Ashfield @ 2012-09-10 18:11 UTC (permalink / raw) To: richard.purdie; +Cc: openembedded-core Updating to 3.4.10 which has been soaking for a bit now, as well as picking up the following meta commits from Tom Z: a82db2f meta: have systemtap use kprobes and uprobes feature d5d5b80 meta: add kprobes support to ktypes/standard b32d373 meta: add kprobes feature d40ed99 meta: have uprobe feature use uprobe.cfg a69d1db meta: add uprobe.cfg Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> --- meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++++---- meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 ++++++++-------- 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb index b2620ea..3b36378 100644 --- a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb +++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb @@ -3,14 +3,14 @@ require recipes-kernel/linux/linux-yocto.inc KBRANCH = "standard/preempt-rt/base" KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" -LINUX_VERSION ?= "3.4.9" +LINUX_VERSION ?= "3.4.10" LINUX_KERNEL_TYPE = "preempt-rt" KMETA = "meta" -SRCREV_machine ?= "9032b1e9daf5b4396f939981c3be95f67802d18c" -SRCREV_machine_qemuppc ?= "08ce190232f89303772b6591ca7daaf2820eb74e" -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" +SRCREV_machine ?= "a35693b1287c0e50cdca33a1b95af0ff48b43cd0" +SRCREV_machine_qemuppc ?= "85a1190530cb5749f5f831670976b163438dc301" +SRCREV_meta ?= "d9d5fc63d8b38705036e946ea77d971d95de11ad" PR = "${INC_PR}.0" PV = "${LINUX_VERSION}+git${SRCPV}" diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb b/meta/recipes-kernel/linux/linux-yocto_3.4.bb index 06bcb9a..7258cba 100644 --- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb +++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb @@ -3,17 +3,17 @@ require recipes-kernel/linux/linux-yocto.inc KBRANCH_DEFAULT = "standard/base" KBRANCH = "${KBRANCH_DEFAULT}" -SRCREV_machine_qemuarm ?= "84d8ee32265eea5d60f57a2f70bd3b9a0fb9213d" -SRCREV_machine_qemumips ?= "ba0e336d4527080233c3c410989d4f351529ee4e" -SRCREV_machine_qemuppc ?= "e82b8a111430e3820b11f507863c4b8e8734ed8e" -SRCREV_machine_qemux86 ?= "0985844fa6235422c67ef269952fa4e765f252f9" -SRCREV_machine_qemux86-64 ?= "0985844fa6235422c67ef269952fa4e765f252f9" -SRCREV_machine ?= "0985844fa6235422c67ef269952fa4e765f252f9" -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" +SRCREV_machine_qemuarm ?= "b15e7b1e9b58b9863bd87778775f86cd8d8880ea" +SRCREV_machine_qemumips ?= "8d5b98f263b5119af2dc30223f311be17173bab9" +SRCREV_machine_qemuppc ?= "b9a720ca38d298ed457f37d099c85771f9164b19" +SRCREV_machine_qemux86 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" +SRCREV_machine_qemux86-64 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" +SRCREV_machine ?= "46d8c757b3be1953f30d6745505d24436e2d6844" +SRCREV_meta ?= "a82db2f0fc3ceebf3cb47e9dd05e4856ff9966ab" SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta" -LINUX_VERSION ?= "3.4.9" +LINUX_VERSION ?= "3.4.10" PR = "${INC_PR}.1" PV = "${LINUX_VERSION}+git${SRCPV}" -- 1.7.5.4 ^ permalink raw reply related [flat|nested] 17+ messages in thread
* Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates 2012-09-10 18:11 ` [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates Bruce Ashfield @ 2012-09-11 4:50 ` Khem Raj 2012-09-11 4:52 ` Bruce Ashfield 2012-09-11 6:59 ` Martin Jansa 1 sibling, 1 reply; 17+ messages in thread From: Khem Raj @ 2012-09-11 4:50 UTC (permalink / raw) To: Bruce Ashfield; +Cc: openembedded-core On (10/09/12 14:11), Bruce Ashfield wrote: > Updating to 3.4.10 which has been soaking for a bit now, as well > as picking up the following meta commits from Tom Z: would it also need bumping linux-libc-headers too ? > > a82db2f meta: have systemtap use kprobes and uprobes feature > d5d5b80 meta: add kprobes support to ktypes/standard > b32d373 meta: add kprobes feature > d40ed99 meta: have uprobe feature use uprobe.cfg > a69d1db meta: add uprobe.cfg > > Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> > --- > meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++++---- > meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 ++++++++-------- > 2 files changed, 12 insertions(+), 12 deletions(-) > > diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb > index b2620ea..3b36378 100644 > --- a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb > +++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb > @@ -3,14 +3,14 @@ require recipes-kernel/linux/linux-yocto.inc > KBRANCH = "standard/preempt-rt/base" > KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" > > -LINUX_VERSION ?= "3.4.9" > +LINUX_VERSION ?= "3.4.10" > LINUX_KERNEL_TYPE = "preempt-rt" > > KMETA = "meta" > > -SRCREV_machine ?= "9032b1e9daf5b4396f939981c3be95f67802d18c" > -SRCREV_machine_qemuppc ?= "08ce190232f89303772b6591ca7daaf2820eb74e" > -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" > +SRCREV_machine ?= "a35693b1287c0e50cdca33a1b95af0ff48b43cd0" > +SRCREV_machine_qemuppc ?= "85a1190530cb5749f5f831670976b163438dc301" > +SRCREV_meta ?= "d9d5fc63d8b38705036e946ea77d971d95de11ad" > > PR = "${INC_PR}.0" > PV = "${LINUX_VERSION}+git${SRCPV}" > diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb b/meta/recipes-kernel/linux/linux-yocto_3.4.bb > index 06bcb9a..7258cba 100644 > --- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb > +++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb > @@ -3,17 +3,17 @@ require recipes-kernel/linux/linux-yocto.inc > KBRANCH_DEFAULT = "standard/base" > KBRANCH = "${KBRANCH_DEFAULT}" > > -SRCREV_machine_qemuarm ?= "84d8ee32265eea5d60f57a2f70bd3b9a0fb9213d" > -SRCREV_machine_qemumips ?= "ba0e336d4527080233c3c410989d4f351529ee4e" > -SRCREV_machine_qemuppc ?= "e82b8a111430e3820b11f507863c4b8e8734ed8e" > -SRCREV_machine_qemux86 ?= "0985844fa6235422c67ef269952fa4e765f252f9" > -SRCREV_machine_qemux86-64 ?= "0985844fa6235422c67ef269952fa4e765f252f9" > -SRCREV_machine ?= "0985844fa6235422c67ef269952fa4e765f252f9" > -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" > +SRCREV_machine_qemuarm ?= "b15e7b1e9b58b9863bd87778775f86cd8d8880ea" > +SRCREV_machine_qemumips ?= "8d5b98f263b5119af2dc30223f311be17173bab9" > +SRCREV_machine_qemuppc ?= "b9a720ca38d298ed457f37d099c85771f9164b19" > +SRCREV_machine_qemux86 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" > +SRCREV_machine_qemux86-64 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" > +SRCREV_machine ?= "46d8c757b3be1953f30d6745505d24436e2d6844" > +SRCREV_meta ?= "a82db2f0fc3ceebf3cb47e9dd05e4856ff9966ab" > > SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta" > > -LINUX_VERSION ?= "3.4.9" > +LINUX_VERSION ?= "3.4.10" > > PR = "${INC_PR}.1" > PV = "${LINUX_VERSION}+git${SRCPV}" > -- > 1.7.5.4 > > > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core -- -Khem ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates 2012-09-11 4:50 ` Khem Raj @ 2012-09-11 4:52 ` Bruce Ashfield 2012-09-11 4:55 ` Khem Raj 0 siblings, 1 reply; 17+ messages in thread From: Bruce Ashfield @ 2012-09-11 4:52 UTC (permalink / raw) To: richard.purdie, openembedded-core On 12-09-11 12:50 AM, Khem Raj wrote: > On (10/09/12 14:11), Bruce Ashfield wrote: >> Updating to 3.4.10 which has been soaking for a bit now, as well >> as picking up the following meta commits from Tom Z: > > would it also need bumping linux-libc-headers too ? There's no new interfaces in the -stable updates, so there's no reason to bump. I typically elect to jump to a 3.x.0 and leave it there, but we had an interim bump that I wouldn't have done .. so we sit at 3.4.3 at the moment (which is still fine). Cheers, Bruce > >> >> a82db2f meta: have systemtap use kprobes and uprobes feature >> d5d5b80 meta: add kprobes support to ktypes/standard >> b32d373 meta: add kprobes feature >> d40ed99 meta: have uprobe feature use uprobe.cfg >> a69d1db meta: add uprobe.cfg >> >> Signed-off-by: Bruce Ashfield<bruce.ashfield@windriver.com> >> --- >> meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++++---- >> meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 ++++++++-------- >> 2 files changed, 12 insertions(+), 12 deletions(-) >> >> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb >> index b2620ea..3b36378 100644 >> --- a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb >> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb >> @@ -3,14 +3,14 @@ require recipes-kernel/linux/linux-yocto.inc >> KBRANCH = "standard/preempt-rt/base" >> KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" >> >> -LINUX_VERSION ?= "3.4.9" >> +LINUX_VERSION ?= "3.4.10" >> LINUX_KERNEL_TYPE = "preempt-rt" >> >> KMETA = "meta" >> >> -SRCREV_machine ?= "9032b1e9daf5b4396f939981c3be95f67802d18c" >> -SRCREV_machine_qemuppc ?= "08ce190232f89303772b6591ca7daaf2820eb74e" >> -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" >> +SRCREV_machine ?= "a35693b1287c0e50cdca33a1b95af0ff48b43cd0" >> +SRCREV_machine_qemuppc ?= "85a1190530cb5749f5f831670976b163438dc301" >> +SRCREV_meta ?= "d9d5fc63d8b38705036e946ea77d971d95de11ad" >> >> PR = "${INC_PR}.0" >> PV = "${LINUX_VERSION}+git${SRCPV}" >> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb b/meta/recipes-kernel/linux/linux-yocto_3.4.bb >> index 06bcb9a..7258cba 100644 >> --- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb >> +++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb >> @@ -3,17 +3,17 @@ require recipes-kernel/linux/linux-yocto.inc >> KBRANCH_DEFAULT = "standard/base" >> KBRANCH = "${KBRANCH_DEFAULT}" >> >> -SRCREV_machine_qemuarm ?= "84d8ee32265eea5d60f57a2f70bd3b9a0fb9213d" >> -SRCREV_machine_qemumips ?= "ba0e336d4527080233c3c410989d4f351529ee4e" >> -SRCREV_machine_qemuppc ?= "e82b8a111430e3820b11f507863c4b8e8734ed8e" >> -SRCREV_machine_qemux86 ?= "0985844fa6235422c67ef269952fa4e765f252f9" >> -SRCREV_machine_qemux86-64 ?= "0985844fa6235422c67ef269952fa4e765f252f9" >> -SRCREV_machine ?= "0985844fa6235422c67ef269952fa4e765f252f9" >> -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" >> +SRCREV_machine_qemuarm ?= "b15e7b1e9b58b9863bd87778775f86cd8d8880ea" >> +SRCREV_machine_qemumips ?= "8d5b98f263b5119af2dc30223f311be17173bab9" >> +SRCREV_machine_qemuppc ?= "b9a720ca38d298ed457f37d099c85771f9164b19" >> +SRCREV_machine_qemux86 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" >> +SRCREV_machine_qemux86-64 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" >> +SRCREV_machine ?= "46d8c757b3be1953f30d6745505d24436e2d6844" >> +SRCREV_meta ?= "a82db2f0fc3ceebf3cb47e9dd05e4856ff9966ab" >> >> SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta" >> >> -LINUX_VERSION ?= "3.4.9" >> +LINUX_VERSION ?= "3.4.10" >> >> PR = "${INC_PR}.1" >> PV = "${LINUX_VERSION}+git${SRCPV}" >> -- >> 1.7.5.4 >> >> >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates 2012-09-11 4:52 ` Bruce Ashfield @ 2012-09-11 4:55 ` Khem Raj 2012-09-11 4:58 ` Bruce Ashfield 0 siblings, 1 reply; 17+ messages in thread From: Khem Raj @ 2012-09-11 4:55 UTC (permalink / raw) To: Bruce Ashfield; +Cc: openembedded-core On (11/09/12 00:52), Bruce Ashfield wrote: > On 12-09-11 12:50 AM, Khem Raj wrote: > >On (10/09/12 14:11), Bruce Ashfield wrote: > >>Updating to 3.4.10 which has been soaking for a bit now, as well > >>as picking up the following meta commits from Tom Z: > > > >would it also need bumping linux-libc-headers too ? > > There's no new interfaces in the -stable updates, so there's no reason > to bump. I typically elect to jump to a 3.x.0 and leave it there, but > we had an interim bump that I wouldn't have done .. so we sit at 3.4.3 > at the moment (which is still fine). OK. Next question is, do stable updates get changes such that we need to bump the linux-libc-headers ? ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates 2012-09-11 4:55 ` Khem Raj @ 2012-09-11 4:58 ` Bruce Ashfield 2012-09-11 5:16 ` Khem Raj 0 siblings, 1 reply; 17+ messages in thread From: Bruce Ashfield @ 2012-09-11 4:58 UTC (permalink / raw) To: richard.purdie, openembedded-core On 12-09-11 12:55 AM, Khem Raj wrote: > On (11/09/12 00:52), Bruce Ashfield wrote: >> On 12-09-11 12:50 AM, Khem Raj wrote: >>> On (10/09/12 14:11), Bruce Ashfield wrote: >>>> Updating to 3.4.10 which has been soaking for a bit now, as well >>>> as picking up the following meta commits from Tom Z: >>> >>> would it also need bumping linux-libc-headers too ? >> >> There's no new interfaces in the -stable updates, so there's no reason >> to bump. I typically elect to jump to a 3.x.0 and leave it there, but >> we had an interim bump that I wouldn't have done .. so we sit at 3.4.3 >> at the moment (which is still fine). > > OK. Next question is, do stable updates get changes such that we need to > bump the linux-libc-headers ? Not that I've ever seen. Since there are no new features or user exported defines that make it into the -stable updates, using the base version headers is reasonable. It saves churn, and keeps all of the QA and testing results directly applicable throughout feature freeze by leaving the the stable. Cheers, Bruce ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates 2012-09-11 4:58 ` Bruce Ashfield @ 2012-09-11 5:16 ` Khem Raj 2012-09-11 5:17 ` Bruce Ashfield 0 siblings, 1 reply; 17+ messages in thread From: Khem Raj @ 2012-09-11 5:16 UTC (permalink / raw) To: Bruce Ashfield; +Cc: openembedded-core On (11/09/12 00:58), Bruce Ashfield wrote: > On 12-09-11 12:55 AM, Khem Raj wrote: > >On (11/09/12 00:52), Bruce Ashfield wrote: > >>On 12-09-11 12:50 AM, Khem Raj wrote: > >>>On (10/09/12 14:11), Bruce Ashfield wrote: > >>>>Updating to 3.4.10 which has been soaking for a bit now, as well > >>>>as picking up the following meta commits from Tom Z: > >>> > >>>would it also need bumping linux-libc-headers too ? > >> > >>There's no new interfaces in the -stable updates, so there's no reason > >>to bump. I typically elect to jump to a 3.x.0 and leave it there, but > >>we had an interim bump that I wouldn't have done .. so we sit at 3.4.3 > >>at the moment (which is still fine). > > > >OK. Next question is, do stable updates get changes such that we need to > >bump the linux-libc-headers ? > > Not that I've ever seen. OK thats what I was expecting to hear so in theory if we always pin linux-libc-headers to major release we are good. say 3.4.0 and then 3.6.0 and so on we really dont need 3.4.1 or later and similarly for other versions. In this case we only bump the linux-libc-headers recipe when we add a new major kernel release Since there are no new features or user exported > defines that make it into the -stable updates, using the base > version headers > is reasonable. It saves churn, and keeps all of the QA and testing > results directly applicable throughout feature freeze by leaving the > the stable. > > Cheers, > > Bruce > > > > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core -- -Khem ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates 2012-09-11 5:16 ` Khem Raj @ 2012-09-11 5:17 ` Bruce Ashfield 2012-09-11 5:22 ` Khem Raj 0 siblings, 1 reply; 17+ messages in thread From: Bruce Ashfield @ 2012-09-11 5:17 UTC (permalink / raw) To: richard.purdie, openembedded-core On 12-09-11 1:16 AM, Khem Raj wrote: > On (11/09/12 00:58), Bruce Ashfield wrote: >> On 12-09-11 12:55 AM, Khem Raj wrote: >>> On (11/09/12 00:52), Bruce Ashfield wrote: >>>> On 12-09-11 12:50 AM, Khem Raj wrote: >>>>> On (10/09/12 14:11), Bruce Ashfield wrote: >>>>>> Updating to 3.4.10 which has been soaking for a bit now, as well >>>>>> as picking up the following meta commits from Tom Z: >>>>> >>>>> would it also need bumping linux-libc-headers too ? >>>> >>>> There's no new interfaces in the -stable updates, so there's no reason >>>> to bump. I typically elect to jump to a 3.x.0 and leave it there, but >>>> we had an interim bump that I wouldn't have done .. so we sit at 3.4.3 >>>> at the moment (which is still fine). >>> >>> OK. Next question is, do stable updates get changes such that we need to >>> bump the linux-libc-headers ? >> >> Not that I've ever seen. > > OK thats what I was expecting to hear > so in theory if we always pin linux-libc-headers to major release we are > good. say 3.4.0 and then 3.6.0 and so on we really dont need 3.4.1 or > later and similarly for other versions. In this case we only bump > the linux-libc-headers recipe when we add a new major kernel release Correct. If you check the mailing list archives, I was a bit surprised to see it go to 3.4.3, but going forward, expect to only see major rev bumps. Cheers, Bruce > > Since there are no new features or user exported >> defines that make it into the -stable updates, using the base >> version headers >> is reasonable. It saves churn, and keeps all of the QA and testing >> results directly applicable throughout feature freeze by leaving the >> the stable. >> >> Cheers, >> >> Bruce >> >> >> >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates 2012-09-11 5:17 ` Bruce Ashfield @ 2012-09-11 5:22 ` Khem Raj 2012-09-11 12:32 ` Bruce Ashfield 0 siblings, 1 reply; 17+ messages in thread From: Khem Raj @ 2012-09-11 5:22 UTC (permalink / raw) To: Bruce Ashfield; +Cc: openembedded-core On (11/09/12 01:17), Bruce Ashfield wrote: > On 12-09-11 1:16 AM, Khem Raj wrote: > >On (11/09/12 00:58), Bruce Ashfield wrote: > >>On 12-09-11 12:55 AM, Khem Raj wrote: > >>>On (11/09/12 00:52), Bruce Ashfield wrote: > >>>>On 12-09-11 12:50 AM, Khem Raj wrote: > >>>>>On (10/09/12 14:11), Bruce Ashfield wrote: > >>>>>>Updating to 3.4.10 which has been soaking for a bit now, as well > >>>>>>as picking up the following meta commits from Tom Z: > >>>>> > >>>>>would it also need bumping linux-libc-headers too ? > >>>> > >>>>There's no new interfaces in the -stable updates, so there's no reason > >>>>to bump. I typically elect to jump to a 3.x.0 and leave it there, but > >>>>we had an interim bump that I wouldn't have done .. so we sit at 3.4.3 > >>>>at the moment (which is still fine). > >>> > >>>OK. Next question is, do stable updates get changes such that we need to > >>>bump the linux-libc-headers ? > >> > >>Not that I've ever seen. > > > >OK thats what I was expecting to hear > >so in theory if we always pin linux-libc-headers to major release we are > >good. say 3.4.0 and then 3.6.0 and so on we really dont need 3.4.1 or > >later and similarly for other versions. In this case we only bump > >the linux-libc-headers recipe when we add a new major kernel release > > Correct. If you check the mailing list archives, I was a bit surprised > to see it go to 3.4.3, but going forward, expect to only see major rev > bumps. yes essentually IIRC I mentioned that recipe should be called blah_3.4.bb and blah_3.6.bb and so on and not really blah_3.4.x etc. OK I am glad we are on same page boundary here :) ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates 2012-09-11 5:22 ` Khem Raj @ 2012-09-11 12:32 ` Bruce Ashfield 0 siblings, 0 replies; 17+ messages in thread From: Bruce Ashfield @ 2012-09-11 12:32 UTC (permalink / raw) To: richard.purdie, openembedded-core On 12-09-11 01:22 AM, Khem Raj wrote: > On (11/09/12 01:17), Bruce Ashfield wrote: >> On 12-09-11 1:16 AM, Khem Raj wrote: >>> On (11/09/12 00:58), Bruce Ashfield wrote: >>>> On 12-09-11 12:55 AM, Khem Raj wrote: >>>>> On (11/09/12 00:52), Bruce Ashfield wrote: >>>>>> On 12-09-11 12:50 AM, Khem Raj wrote: >>>>>>> On (10/09/12 14:11), Bruce Ashfield wrote: >>>>>>>> Updating to 3.4.10 which has been soaking for a bit now, as well >>>>>>>> as picking up the following meta commits from Tom Z: >>>>>>> >>>>>>> would it also need bumping linux-libc-headers too ? >>>>>> >>>>>> There's no new interfaces in the -stable updates, so there's no reason >>>>>> to bump. I typically elect to jump to a 3.x.0 and leave it there, but >>>>>> we had an interim bump that I wouldn't have done .. so we sit at 3.4.3 >>>>>> at the moment (which is still fine). >>>>> >>>>> OK. Next question is, do stable updates get changes such that we need to >>>>> bump the linux-libc-headers ? >>>> >>>> Not that I've ever seen. >>> >>> OK thats what I was expecting to hear >>> so in theory if we always pin linux-libc-headers to major release we are >>> good. say 3.4.0 and then 3.6.0 and so on we really dont need 3.4.1 or >>> later and similarly for other versions. In this case we only bump >>> the linux-libc-headers recipe when we add a new major kernel release >> >> Correct. If you check the mailing list archives, I was a bit surprised >> to see it go to 3.4.3, but going forward, expect to only see major rev >> bumps. > > yes essentually IIRC I mentioned that recipe should be called > blah_3.4.bb and blah_3.6.bb and so on and not really blah_3.4.x etc. > OK I am glad we are on same page boundary here :) Agreed. We are in sync. Bruce ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates 2012-09-10 18:11 ` [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates Bruce Ashfield 2012-09-11 4:50 ` Khem Raj @ 2012-09-11 6:59 ` Martin Jansa [not found] ` <504F2F2E.3080507@windriver.com> 1 sibling, 1 reply; 17+ messages in thread From: Martin Jansa @ 2012-09-11 6:59 UTC (permalink / raw) To: Bruce Ashfield On Mon, Sep 10, 2012 at 8:11 PM, Bruce Ashfield <bruce.ashfield@windriver.com> wrote: > Updating to 3.4.10 which has been soaking for a bit now, as well > as picking up the following meta commits from Tom Z: > > a82db2f meta: have systemtap use kprobes and uprobes feature > d5d5b80 meta: add kprobes support to ktypes/standard > b32d373 meta: add kprobes feature > d40ed99 meta: have uprobe feature use uprobe.cfg > a69d1db meta: add uprobe.cfg > > Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> > --- > meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++++---- > meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 ++++++++-------- > 2 files changed, 12 insertions(+), 12 deletions(-) > > diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb > index b2620ea..3b36378 100644 > --- a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb > +++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb > @@ -3,14 +3,14 @@ require recipes-kernel/linux/linux-yocto.inc > KBRANCH = "standard/preempt-rt/base" > KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" > > -LINUX_VERSION ?= "3.4.9" > +LINUX_VERSION ?= "3.4.10" > LINUX_KERNEL_TYPE = "preempt-rt" > > KMETA = "meta" > > -SRCREV_machine ?= "9032b1e9daf5b4396f939981c3be95f67802d18c" > -SRCREV_machine_qemuppc ?= "08ce190232f89303772b6591ca7daaf2820eb74e" > -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" > +SRCREV_machine ?= "a35693b1287c0e50cdca33a1b95af0ff48b43cd0" > +SRCREV_machine_qemuppc ?= "85a1190530cb5749f5f831670976b163438dc301" > +SRCREV_meta ?= "d9d5fc63d8b38705036e946ea77d971d95de11ad" > > PR = "${INC_PR}.0" > PV = "${LINUX_VERSION}+git${SRCPV}" > diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb b/meta/recipes-kernel/linux/linux-yocto_3.4.bb > index 06bcb9a..7258cba 100644 > --- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb > +++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb > @@ -3,17 +3,17 @@ require recipes-kernel/linux/linux-yocto.inc > KBRANCH_DEFAULT = "standard/base" > KBRANCH = "${KBRANCH_DEFAULT}" > > -SRCREV_machine_qemuarm ?= "84d8ee32265eea5d60f57a2f70bd3b9a0fb9213d" > -SRCREV_machine_qemumips ?= "ba0e336d4527080233c3c410989d4f351529ee4e" > -SRCREV_machine_qemuppc ?= "e82b8a111430e3820b11f507863c4b8e8734ed8e" > -SRCREV_machine_qemux86 ?= "0985844fa6235422c67ef269952fa4e765f252f9" > -SRCREV_machine_qemux86-64 ?= "0985844fa6235422c67ef269952fa4e765f252f9" > -SRCREV_machine ?= "0985844fa6235422c67ef269952fa4e765f252f9" > -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" > +SRCREV_machine_qemuarm ?= "b15e7b1e9b58b9863bd87778775f86cd8d8880ea" > +SRCREV_machine_qemumips ?= "8d5b98f263b5119af2dc30223f311be17173bab9" > +SRCREV_machine_qemuppc ?= "b9a720ca38d298ed457f37d099c85771f9164b19" > +SRCREV_machine_qemux86 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" > +SRCREV_machine_qemux86-64 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" > +SRCREV_machine ?= "46d8c757b3be1953f30d6745505d24436e2d6844" > +SRCREV_meta ?= "a82db2f0fc3ceebf3cb47e9dd05e4856ff9966ab" Doesn't different SRCREV_machine for each MACHINE cause LOCALCOUNT in SRCPV incrementing on each MACHINE switch? They are stored under same key: sqlite> select * from BB_URI_LOCALCOUNT where key like '%linux-yocto-3.4%'; git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/base-linux-yocto_rev|84d8ee32265eea5d60f57a2f70bd3b9a0fb9213d git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/base-linux-yocto_count|16 git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto_rev|463299bc2e533e1bd38b0053ae7b210980f269c3 git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto_count|9 git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/common-pc-64/base-linux-yocto_rev|19f7e43b54aef08d58135ed2a897d77b624b320a git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/common-pc-64/base-linux-yocto_count|7 git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/preempt-rt/base-linux-yocto-rt_rev|9032b1e9daf5b4396f939981c3be95f67802d18c git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/preempt-rt/base-linux-yocto-rt_count|10 git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto-rt_rev|463299bc2e533e1bd38b0053ae7b210980f269c3 git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto-rt_count|8 So I guess if you build linux-yocto-3.4 for qemuarm, qemux86-64, then switch back to qemuarm you'll see linux-yocto built again, same source, but different SRCPV (LOCALCOUNT). Cheers, ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <504F2F2E.3080507@windriver.com>]
* Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates [not found] ` <504F2F2E.3080507@windriver.com> @ 2012-09-11 12:37 ` Martin Jansa 2012-09-11 13:27 ` Bruce Ashfield 0 siblings, 1 reply; 17+ messages in thread From: Martin Jansa @ 2012-09-11 12:37 UTC (permalink / raw) To: Bruce Ashfield; +Cc: openembedded-core [-- Attachment #1: Type: text/plain, Size: 5519 bytes --] On Tue, Sep 11, 2012 at 08:31:42AM -0400, Bruce Ashfield wrote: > On 12-09-11 02:59 AM, Martin Jansa wrote: > > On Mon, Sep 10, 2012 at 8:11 PM, Bruce Ashfield > > <bruce.ashfield@windriver.com> wrote: > >> Updating to 3.4.10 which has been soaking for a bit now, as well > >> as picking up the following meta commits from Tom Z: > >> > >> a82db2f meta: have systemtap use kprobes and uprobes feature > >> d5d5b80 meta: add kprobes support to ktypes/standard > >> b32d373 meta: add kprobes feature > >> d40ed99 meta: have uprobe feature use uprobe.cfg > >> a69d1db meta: add uprobe.cfg > >> > >> Signed-off-by: Bruce Ashfield<bruce.ashfield@windriver.com> > >> --- > >> meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++++---- > >> meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 ++++++++-------- > >> 2 files changed, 12 insertions(+), 12 deletions(-) > >> > >> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb > >> index b2620ea..3b36378 100644 > >> --- a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb > >> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb > >> @@ -3,14 +3,14 @@ require recipes-kernel/linux/linux-yocto.inc > >> KBRANCH = "standard/preempt-rt/base" > >> KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" > >> > >> -LINUX_VERSION ?= "3.4.9" > >> +LINUX_VERSION ?= "3.4.10" > >> LINUX_KERNEL_TYPE = "preempt-rt" > >> > >> KMETA = "meta" > >> > >> -SRCREV_machine ?= "9032b1e9daf5b4396f939981c3be95f67802d18c" > >> -SRCREV_machine_qemuppc ?= "08ce190232f89303772b6591ca7daaf2820eb74e" > >> -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" > >> +SRCREV_machine ?= "a35693b1287c0e50cdca33a1b95af0ff48b43cd0" > >> +SRCREV_machine_qemuppc ?= "85a1190530cb5749f5f831670976b163438dc301" > >> +SRCREV_meta ?= "d9d5fc63d8b38705036e946ea77d971d95de11ad" > >> > >> PR = "${INC_PR}.0" > >> PV = "${LINUX_VERSION}+git${SRCPV}" > >> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb b/meta/recipes-kernel/linux/linux-yocto_3.4.bb > >> index 06bcb9a..7258cba 100644 > >> --- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb > >> +++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb > >> @@ -3,17 +3,17 @@ require recipes-kernel/linux/linux-yocto.inc > >> KBRANCH_DEFAULT = "standard/base" > >> KBRANCH = "${KBRANCH_DEFAULT}" > >> > >> -SRCREV_machine_qemuarm ?= "84d8ee32265eea5d60f57a2f70bd3b9a0fb9213d" > >> -SRCREV_machine_qemumips ?= "ba0e336d4527080233c3c410989d4f351529ee4e" > >> -SRCREV_machine_qemuppc ?= "e82b8a111430e3820b11f507863c4b8e8734ed8e" > >> -SRCREV_machine_qemux86 ?= "0985844fa6235422c67ef269952fa4e765f252f9" > >> -SRCREV_machine_qemux86-64 ?= "0985844fa6235422c67ef269952fa4e765f252f9" > >> -SRCREV_machine ?= "0985844fa6235422c67ef269952fa4e765f252f9" > >> -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" > >> +SRCREV_machine_qemuarm ?= "b15e7b1e9b58b9863bd87778775f86cd8d8880ea" > >> +SRCREV_machine_qemumips ?= "8d5b98f263b5119af2dc30223f311be17173bab9" > >> +SRCREV_machine_qemuppc ?= "b9a720ca38d298ed457f37d099c85771f9164b19" > >> +SRCREV_machine_qemux86 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" > >> +SRCREV_machine_qemux86-64 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" > >> +SRCREV_machine ?= "46d8c757b3be1953f30d6745505d24436e2d6844" > >> +SRCREV_meta ?= "a82db2f0fc3ceebf3cb47e9dd05e4856ff9966ab" > > > > Doesn't different SRCREV_machine for each MACHINE cause LOCALCOUNT in > > SRCPV incrementing on each MACHINE switch? > > > > They are stored under same key: > > sqlite> select * from BB_URI_LOCALCOUNT where key like '%linux-yocto-3.4%'; > > git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/base-linux-yocto_rev|84d8ee32265eea5d60f57a2f70bd3b9a0fb9213d > > git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/base-linux-yocto_count|16 > > git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto_rev|463299bc2e533e1bd38b0053ae7b210980f269c3 > > git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto_count|9 > > git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/common-pc-64/base-linux-yocto_rev|19f7e43b54aef08d58135ed2a897d77b624b320a > > git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/common-pc-64/base-linux-yocto_count|7 > > git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/preempt-rt/base-linux-yocto-rt_rev|9032b1e9daf5b4396f939981c3be95f67802d18c > > git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/preempt-rt/base-linux-yocto-rt_count|10 > > git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto-rt_rev|463299bc2e533e1bd38b0053ae7b210980f269c3 > > git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto-rt_count|8 > > > > So I guess if you build linux-yocto-3.4 for qemuarm, qemux86-64, then > > switch back to qemuarm you'll see linux-yocto built again, same > > source, but different SRCPV (LOCALCOUNT). > > That does look to be the case, and it matches what I've observed > over time. I'm not sure of an alternative at the moment, since the > fetcher is such a cranky beast with respect to fetching changes to > the right machine branches. Why not remove it from SRCREV_FORMAT, keep only meta SRCPV and just bump PR when SRCREV of some machine kbranch is changed? Current SRCREV_FORMAT doesn't show which branch it was so it doesn't make it much worse to find what sources were used to build. Cheers, -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates 2012-09-11 12:37 ` Martin Jansa @ 2012-09-11 13:27 ` Bruce Ashfield 2012-09-11 13:33 ` Martin Jansa 0 siblings, 1 reply; 17+ messages in thread From: Bruce Ashfield @ 2012-09-11 13:27 UTC (permalink / raw) To: Martin Jansa; +Cc: openembedded-core On 12-09-11 08:37 AM, Martin Jansa wrote: > On Tue, Sep 11, 2012 at 08:31:42AM -0400, Bruce Ashfield wrote: >> On 12-09-11 02:59 AM, Martin Jansa wrote: >>> On Mon, Sep 10, 2012 at 8:11 PM, Bruce Ashfield >>> <bruce.ashfield@windriver.com> wrote: >>>> Updating to 3.4.10 which has been soaking for a bit now, as well >>>> as picking up the following meta commits from Tom Z: >>>> >>>> a82db2f meta: have systemtap use kprobes and uprobes feature >>>> d5d5b80 meta: add kprobes support to ktypes/standard >>>> b32d373 meta: add kprobes feature >>>> d40ed99 meta: have uprobe feature use uprobe.cfg >>>> a69d1db meta: add uprobe.cfg >>>> >>>> Signed-off-by: Bruce Ashfield<bruce.ashfield@windriver.com> >>>> --- >>>> meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++++---- >>>> meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 ++++++++-------- >>>> 2 files changed, 12 insertions(+), 12 deletions(-) >>>> >>>> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb >>>> index b2620ea..3b36378 100644 >>>> --- a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb >>>> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb >>>> @@ -3,14 +3,14 @@ require recipes-kernel/linux/linux-yocto.inc >>>> KBRANCH = "standard/preempt-rt/base" >>>> KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" >>>> >>>> -LINUX_VERSION ?= "3.4.9" >>>> +LINUX_VERSION ?= "3.4.10" >>>> LINUX_KERNEL_TYPE = "preempt-rt" >>>> >>>> KMETA = "meta" >>>> >>>> -SRCREV_machine ?= "9032b1e9daf5b4396f939981c3be95f67802d18c" >>>> -SRCREV_machine_qemuppc ?= "08ce190232f89303772b6591ca7daaf2820eb74e" >>>> -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" >>>> +SRCREV_machine ?= "a35693b1287c0e50cdca33a1b95af0ff48b43cd0" >>>> +SRCREV_machine_qemuppc ?= "85a1190530cb5749f5f831670976b163438dc301" >>>> +SRCREV_meta ?= "d9d5fc63d8b38705036e946ea77d971d95de11ad" >>>> >>>> PR = "${INC_PR}.0" >>>> PV = "${LINUX_VERSION}+git${SRCPV}" >>>> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb b/meta/recipes-kernel/linux/linux-yocto_3.4.bb >>>> index 06bcb9a..7258cba 100644 >>>> --- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb >>>> +++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb >>>> @@ -3,17 +3,17 @@ require recipes-kernel/linux/linux-yocto.inc >>>> KBRANCH_DEFAULT = "standard/base" >>>> KBRANCH = "${KBRANCH_DEFAULT}" >>>> >>>> -SRCREV_machine_qemuarm ?= "84d8ee32265eea5d60f57a2f70bd3b9a0fb9213d" >>>> -SRCREV_machine_qemumips ?= "ba0e336d4527080233c3c410989d4f351529ee4e" >>>> -SRCREV_machine_qemuppc ?= "e82b8a111430e3820b11f507863c4b8e8734ed8e" >>>> -SRCREV_machine_qemux86 ?= "0985844fa6235422c67ef269952fa4e765f252f9" >>>> -SRCREV_machine_qemux86-64 ?= "0985844fa6235422c67ef269952fa4e765f252f9" >>>> -SRCREV_machine ?= "0985844fa6235422c67ef269952fa4e765f252f9" >>>> -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" >>>> +SRCREV_machine_qemuarm ?= "b15e7b1e9b58b9863bd87778775f86cd8d8880ea" >>>> +SRCREV_machine_qemumips ?= "8d5b98f263b5119af2dc30223f311be17173bab9" >>>> +SRCREV_machine_qemuppc ?= "b9a720ca38d298ed457f37d099c85771f9164b19" >>>> +SRCREV_machine_qemux86 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" >>>> +SRCREV_machine_qemux86-64 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" >>>> +SRCREV_machine ?= "46d8c757b3be1953f30d6745505d24436e2d6844" >>>> +SRCREV_meta ?= "a82db2f0fc3ceebf3cb47e9dd05e4856ff9966ab" >>> >>> Doesn't different SRCREV_machine for each MACHINE cause LOCALCOUNT in >>> SRCPV incrementing on each MACHINE switch? >>> >>> They are stored under same key: >>> sqlite> select * from BB_URI_LOCALCOUNT where key like '%linux-yocto-3.4%'; >>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/base-linux-yocto_rev|84d8ee32265eea5d60f57a2f70bd3b9a0fb9213d >>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/base-linux-yocto_count|16 >>> git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto_rev|463299bc2e533e1bd38b0053ae7b210980f269c3 >>> git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto_count|9 >>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/common-pc-64/base-linux-yocto_rev|19f7e43b54aef08d58135ed2a897d77b624b320a >>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/common-pc-64/base-linux-yocto_count|7 >>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/preempt-rt/base-linux-yocto-rt_rev|9032b1e9daf5b4396f939981c3be95f67802d18c >>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/preempt-rt/base-linux-yocto-rt_count|10 >>> git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto-rt_rev|463299bc2e533e1bd38b0053ae7b210980f269c3 >>> git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto-rt_count|8 >>> >>> So I guess if you build linux-yocto-3.4 for qemuarm, qemux86-64, then >>> switch back to qemuarm you'll see linux-yocto built again, same >>> source, but different SRCPV (LOCALCOUNT). >> >> That does look to be the case, and it matches what I've observed >> over time. I'm not sure of an alternative at the moment, since the >> fetcher is such a cranky beast with respect to fetching changes to >> the right machine branches. > > Why not remove it from SRCREV_FORMAT, keep only meta SRCPV and just bump > PR when SRCREV of some machine kbranch is changed? I like the sound of it, but as far as I know, wouldn't that fix the package revision, but cause the fetcher problems ? I've added Richard to the cc, since I'm not sure what the current status of the fetcher is in this regard. If I don't bump the SRCREV for the machines, and just bump the PR, there's nothing in place to trigger the fetcher when only machine changes have been made to one of the branches, and conversely there's no explicit value set to inhibit a machine's SRCREV when you don't want the end of the branch to be built (I always build the end, but other layers inhibit SRCREV frequently to throttle their updates). If there's a better way that keeps the rebuilds to a minimum, but doesn't break the fetcher and those other use cases .. I'm more than happy to switch to it :) Bruce > > Current SRCREV_FORMAT doesn't show which branch it was so it doesn't > make it much worse to find what sources were used to build. > > Cheers, > ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates 2012-09-11 13:27 ` Bruce Ashfield @ 2012-09-11 13:33 ` Martin Jansa 2012-09-11 19:40 ` Bruce Ashfield 0 siblings, 1 reply; 17+ messages in thread From: Martin Jansa @ 2012-09-11 13:33 UTC (permalink / raw) To: Bruce Ashfield; +Cc: openembedded-core [-- Attachment #1: Type: text/plain, Size: 7092 bytes --] On Tue, Sep 11, 2012 at 09:27:50AM -0400, Bruce Ashfield wrote: > On 12-09-11 08:37 AM, Martin Jansa wrote: > > On Tue, Sep 11, 2012 at 08:31:42AM -0400, Bruce Ashfield wrote: > >> On 12-09-11 02:59 AM, Martin Jansa wrote: > >>> On Mon, Sep 10, 2012 at 8:11 PM, Bruce Ashfield > >>> <bruce.ashfield@windriver.com> wrote: > >>>> Updating to 3.4.10 which has been soaking for a bit now, as well > >>>> as picking up the following meta commits from Tom Z: > >>>> > >>>> a82db2f meta: have systemtap use kprobes and uprobes feature > >>>> d5d5b80 meta: add kprobes support to ktypes/standard > >>>> b32d373 meta: add kprobes feature > >>>> d40ed99 meta: have uprobe feature use uprobe.cfg > >>>> a69d1db meta: add uprobe.cfg > >>>> > >>>> Signed-off-by: Bruce Ashfield<bruce.ashfield@windriver.com> > >>>> --- > >>>> meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++++---- > >>>> meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 ++++++++-------- > >>>> 2 files changed, 12 insertions(+), 12 deletions(-) > >>>> > >>>> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb > >>>> index b2620ea..3b36378 100644 > >>>> --- a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb > >>>> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb > >>>> @@ -3,14 +3,14 @@ require recipes-kernel/linux/linux-yocto.inc > >>>> KBRANCH = "standard/preempt-rt/base" > >>>> KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" > >>>> > >>>> -LINUX_VERSION ?= "3.4.9" > >>>> +LINUX_VERSION ?= "3.4.10" > >>>> LINUX_KERNEL_TYPE = "preempt-rt" > >>>> > >>>> KMETA = "meta" > >>>> > >>>> -SRCREV_machine ?= "9032b1e9daf5b4396f939981c3be95f67802d18c" > >>>> -SRCREV_machine_qemuppc ?= "08ce190232f89303772b6591ca7daaf2820eb74e" > >>>> -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" > >>>> +SRCREV_machine ?= "a35693b1287c0e50cdca33a1b95af0ff48b43cd0" > >>>> +SRCREV_machine_qemuppc ?= "85a1190530cb5749f5f831670976b163438dc301" > >>>> +SRCREV_meta ?= "d9d5fc63d8b38705036e946ea77d971d95de11ad" > >>>> > >>>> PR = "${INC_PR}.0" > >>>> PV = "${LINUX_VERSION}+git${SRCPV}" > >>>> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb b/meta/recipes-kernel/linux/linux-yocto_3.4.bb > >>>> index 06bcb9a..7258cba 100644 > >>>> --- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb > >>>> +++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb > >>>> @@ -3,17 +3,17 @@ require recipes-kernel/linux/linux-yocto.inc > >>>> KBRANCH_DEFAULT = "standard/base" > >>>> KBRANCH = "${KBRANCH_DEFAULT}" > >>>> > >>>> -SRCREV_machine_qemuarm ?= "84d8ee32265eea5d60f57a2f70bd3b9a0fb9213d" > >>>> -SRCREV_machine_qemumips ?= "ba0e336d4527080233c3c410989d4f351529ee4e" > >>>> -SRCREV_machine_qemuppc ?= "e82b8a111430e3820b11f507863c4b8e8734ed8e" > >>>> -SRCREV_machine_qemux86 ?= "0985844fa6235422c67ef269952fa4e765f252f9" > >>>> -SRCREV_machine_qemux86-64 ?= "0985844fa6235422c67ef269952fa4e765f252f9" > >>>> -SRCREV_machine ?= "0985844fa6235422c67ef269952fa4e765f252f9" > >>>> -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" > >>>> +SRCREV_machine_qemuarm ?= "b15e7b1e9b58b9863bd87778775f86cd8d8880ea" > >>>> +SRCREV_machine_qemumips ?= "8d5b98f263b5119af2dc30223f311be17173bab9" > >>>> +SRCREV_machine_qemuppc ?= "b9a720ca38d298ed457f37d099c85771f9164b19" > >>>> +SRCREV_machine_qemux86 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" > >>>> +SRCREV_machine_qemux86-64 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" > >>>> +SRCREV_machine ?= "46d8c757b3be1953f30d6745505d24436e2d6844" > >>>> +SRCREV_meta ?= "a82db2f0fc3ceebf3cb47e9dd05e4856ff9966ab" > >>> > >>> Doesn't different SRCREV_machine for each MACHINE cause LOCALCOUNT in > >>> SRCPV incrementing on each MACHINE switch? > >>> > >>> They are stored under same key: > >>> sqlite> select * from BB_URI_LOCALCOUNT where key like '%linux-yocto-3.4%'; > >>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/base-linux-yocto_rev|84d8ee32265eea5d60f57a2f70bd3b9a0fb9213d > >>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/base-linux-yocto_count|16 > >>> git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto_rev|463299bc2e533e1bd38b0053ae7b210980f269c3 > >>> git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto_count|9 > >>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/common-pc-64/base-linux-yocto_rev|19f7e43b54aef08d58135ed2a897d77b624b320a > >>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/common-pc-64/base-linux-yocto_count|7 > >>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/preempt-rt/base-linux-yocto-rt_rev|9032b1e9daf5b4396f939981c3be95f67802d18c > >>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/preempt-rt/base-linux-yocto-rt_count|10 > >>> git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto-rt_rev|463299bc2e533e1bd38b0053ae7b210980f269c3 > >>> git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto-rt_count|8 > >>> > >>> So I guess if you build linux-yocto-3.4 for qemuarm, qemux86-64, then > >>> switch back to qemuarm you'll see linux-yocto built again, same > >>> source, but different SRCPV (LOCALCOUNT). > >> > >> That does look to be the case, and it matches what I've observed > >> over time. I'm not sure of an alternative at the moment, since the > >> fetcher is such a cranky beast with respect to fetching changes to > >> the right machine branches. > > > > Why not remove it from SRCREV_FORMAT, keep only meta SRCPV and just bump > > PR when SRCREV of some machine kbranch is changed? > > I like the sound of it, but as far as I know, wouldn't that fix the > package revision, but cause the fetcher problems ? I've added Richard > to the cc, since I'm not sure what the current status of the fetcher > is in this regard. > > If I don't bump the SRCREV for the machines, and just bump the PR, > there's nothing in place to trigger the fetcher when only machine > changes have been made to one of the branches, and conversely there's PR bump will trigger recipe rebuild and while rebuilding fetcher will download revision set by SRCREV, why shoudln't it? Only disadvantage I see is that PR bump is "global" so all machines get rebuilt when you bump it only because of one machine changing SRCREV, but that's still better then rebuilding without any change in sources at all. Cheers, > no explicit value set to inhibit a machine's SRCREV when you don't > want the end of the branch to be built (I always build the end, but > other layers inhibit SRCREV frequently to throttle their updates). > > If there's a better way that keeps the rebuilds to a minimum, but > doesn't break the fetcher and those other use cases .. I'm more than > happy to switch to it :) > > Bruce > > > > > Current SRCREV_FORMAT doesn't show which branch it was so it doesn't > > make it much worse to find what sources were used to build. > > > > Cheers, > > > -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates 2012-09-11 13:33 ` Martin Jansa @ 2012-09-11 19:40 ` Bruce Ashfield 0 siblings, 0 replies; 17+ messages in thread From: Bruce Ashfield @ 2012-09-11 19:40 UTC (permalink / raw) To: Martin Jansa; +Cc: openembedded-core On 12-09-11 09:33 AM, Martin Jansa wrote: > On Tue, Sep 11, 2012 at 09:27:50AM -0400, Bruce Ashfield wrote: >> On 12-09-11 08:37 AM, Martin Jansa wrote: >>> On Tue, Sep 11, 2012 at 08:31:42AM -0400, Bruce Ashfield wrote: >>>> On 12-09-11 02:59 AM, Martin Jansa wrote: >>>>> On Mon, Sep 10, 2012 at 8:11 PM, Bruce Ashfield >>>>> <bruce.ashfield@windriver.com> wrote: >>>>>> Updating to 3.4.10 which has been soaking for a bit now, as well >>>>>> as picking up the following meta commits from Tom Z: >>>>>> >>>>>> a82db2f meta: have systemtap use kprobes and uprobes feature >>>>>> d5d5b80 meta: add kprobes support to ktypes/standard >>>>>> b32d373 meta: add kprobes feature >>>>>> d40ed99 meta: have uprobe feature use uprobe.cfg >>>>>> a69d1db meta: add uprobe.cfg >>>>>> >>>>>> Signed-off-by: Bruce Ashfield<bruce.ashfield@windriver.com> >>>>>> --- >>>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++++---- >>>>>> meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 ++++++++-------- >>>>>> 2 files changed, 12 insertions(+), 12 deletions(-) >>>>>> >>>>>> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb >>>>>> index b2620ea..3b36378 100644 >>>>>> --- a/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb >>>>>> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb >>>>>> @@ -3,14 +3,14 @@ require recipes-kernel/linux/linux-yocto.inc >>>>>> KBRANCH = "standard/preempt-rt/base" >>>>>> KBRANCH_qemuppc = "standard/preempt-rt/qemuppc" >>>>>> >>>>>> -LINUX_VERSION ?= "3.4.9" >>>>>> +LINUX_VERSION ?= "3.4.10" >>>>>> LINUX_KERNEL_TYPE = "preempt-rt" >>>>>> >>>>>> KMETA = "meta" >>>>>> >>>>>> -SRCREV_machine ?= "9032b1e9daf5b4396f939981c3be95f67802d18c" >>>>>> -SRCREV_machine_qemuppc ?= "08ce190232f89303772b6591ca7daaf2820eb74e" >>>>>> -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" >>>>>> +SRCREV_machine ?= "a35693b1287c0e50cdca33a1b95af0ff48b43cd0" >>>>>> +SRCREV_machine_qemuppc ?= "85a1190530cb5749f5f831670976b163438dc301" >>>>>> +SRCREV_meta ?= "d9d5fc63d8b38705036e946ea77d971d95de11ad" >>>>>> >>>>>> PR = "${INC_PR}.0" >>>>>> PV = "${LINUX_VERSION}+git${SRCPV}" >>>>>> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb b/meta/recipes-kernel/linux/linux-yocto_3.4.bb >>>>>> index 06bcb9a..7258cba 100644 >>>>>> --- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb >>>>>> +++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb >>>>>> @@ -3,17 +3,17 @@ require recipes-kernel/linux/linux-yocto.inc >>>>>> KBRANCH_DEFAULT = "standard/base" >>>>>> KBRANCH = "${KBRANCH_DEFAULT}" >>>>>> >>>>>> -SRCREV_machine_qemuarm ?= "84d8ee32265eea5d60f57a2f70bd3b9a0fb9213d" >>>>>> -SRCREV_machine_qemumips ?= "ba0e336d4527080233c3c410989d4f351529ee4e" >>>>>> -SRCREV_machine_qemuppc ?= "e82b8a111430e3820b11f507863c4b8e8734ed8e" >>>>>> -SRCREV_machine_qemux86 ?= "0985844fa6235422c67ef269952fa4e765f252f9" >>>>>> -SRCREV_machine_qemux86-64 ?= "0985844fa6235422c67ef269952fa4e765f252f9" >>>>>> -SRCREV_machine ?= "0985844fa6235422c67ef269952fa4e765f252f9" >>>>>> -SRCREV_meta ?= "463299bc2e533e1bd38b0053ae7b210980f269c3" >>>>>> +SRCREV_machine_qemuarm ?= "b15e7b1e9b58b9863bd87778775f86cd8d8880ea" >>>>>> +SRCREV_machine_qemumips ?= "8d5b98f263b5119af2dc30223f311be17173bab9" >>>>>> +SRCREV_machine_qemuppc ?= "b9a720ca38d298ed457f37d099c85771f9164b19" >>>>>> +SRCREV_machine_qemux86 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" >>>>>> +SRCREV_machine_qemux86-64 ?= "46d8c757b3be1953f30d6745505d24436e2d6844" >>>>>> +SRCREV_machine ?= "46d8c757b3be1953f30d6745505d24436e2d6844" >>>>>> +SRCREV_meta ?= "a82db2f0fc3ceebf3cb47e9dd05e4856ff9966ab" >>>>> >>>>> Doesn't different SRCREV_machine for each MACHINE cause LOCALCOUNT in >>>>> SRCPV incrementing on each MACHINE switch? >>>>> >>>>> They are stored under same key: >>>>> sqlite> select * from BB_URI_LOCALCOUNT where key like '%linux-yocto-3.4%'; >>>>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/base-linux-yocto_rev|84d8ee32265eea5d60f57a2f70bd3b9a0fb9213d >>>>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/base-linux-yocto_count|16 >>>>> git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto_rev|463299bc2e533e1bd38b0053ae7b210980f269c3 >>>>> git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto_count|9 >>>>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/common-pc-64/base-linux-yocto_rev|19f7e43b54aef08d58135ed2a897d77b624b320a >>>>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/common-pc-64/base-linux-yocto_count|7 >>>>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/preempt-rt/base-linux-yocto-rt_rev|9032b1e9daf5b4396f939981c3be95f67802d18c >>>>> git:git.yoctoproject.org.linux-yocto-3.4.gitstandard/preempt-rt/base-linux-yocto-rt_count|10 >>>>> git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto-rt_rev|463299bc2e533e1bd38b0053ae7b210980f269c3 >>>>> git:git.yoctoproject.org.linux-yocto-3.4.gitmeta-linux-yocto-rt_count|8 >>>>> >>>>> So I guess if you build linux-yocto-3.4 for qemuarm, qemux86-64, then >>>>> switch back to qemuarm you'll see linux-yocto built again, same >>>>> source, but different SRCPV (LOCALCOUNT). >>>> >>>> That does look to be the case, and it matches what I've observed >>>> over time. I'm not sure of an alternative at the moment, since the >>>> fetcher is such a cranky beast with respect to fetching changes to >>>> the right machine branches. >>> >>> Why not remove it from SRCREV_FORMAT, keep only meta SRCPV and just bump >>> PR when SRCREV of some machine kbranch is changed? >> >> I like the sound of it, but as far as I know, wouldn't that fix the >> package revision, but cause the fetcher problems ? I've added Richard >> to the cc, since I'm not sure what the current status of the fetcher >> is in this regard. >> >> If I don't bump the SRCREV for the machines, and just bump the PR, >> there's nothing in place to trigger the fetcher when only machine >> changes have been made to one of the branches, and conversely there's > > PR bump will trigger recipe rebuild and while rebuilding fetcher will > download revision set by SRCREV, why shoudln't it? It definitely should .. but the fetcher has proven me wrong before. > > Only disadvantage I see is that PR bump is "global" so all machines get > rebuilt when you bump it only because of one machine changing SRCREV, > but that's still better then rebuilding without any change in sources at > all. .. and I staring at this a bit, I think I'm catching up (not enough coffee this morning and too little sleep). I think I mentally mangled this to include dropping the machine SRCREV from the recipe, where you are talking about dropping the from the PV and SRCREV_FORMAT. If in fact the fetcher will update the machine SRCREV on a PR bump, then this should work. But one stupid question, if machine has been removed from the SRCREV format, is the fetcher really going to trigger ? A quick look at the fetcher code doesn't leave me convinced ... Bruce > > Cheers, > >> no explicit value set to inhibit a machine's SRCREV when you don't >> want the end of the branch to be built (I always build the end, but >> other layers inhibit SRCREV frequently to throttle their updates). >> >> If there's a better way that keeps the rebuilds to a minimum, but >> doesn't break the fetcher and those other use cases .. I'm more than >> happy to switch to it :) >> >> Bruce >> >>> >>> Current SRCREV_FORMAT doesn't show which branch it was so it doesn't >>> make it much worse to find what sources were used to build. >>> >>> Cheers, >>> >> > ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [PATCH 0/1] linux-yocto: 3.4 kernel updates 2012-09-10 18:11 [PATCH 0/1] linux-yocto: 3.4 kernel updates Bruce Ashfield 2012-09-10 18:11 ` [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates Bruce Ashfield @ 2012-09-10 18:14 ` Bruce Ashfield 2012-09-12 17:26 ` Saul Wold 2 siblings, 0 replies; 17+ messages in thread From: Bruce Ashfield @ 2012-09-10 18:14 UTC (permalink / raw) To: richard.purdie; +Cc: openembedded-core On Mon, Sep 10, 2012 at 2:11 PM, Bruce Ashfield <bruce.ashfield@windriver.com> wrote: > Richard/Saul, > > Here's a small bump to 3.4.10 (32 commits) and an update to > pickup some configuration changes from TomZ (no impact on existing > features). All in all, it's a nice set of small fixes, with no risk. s/no/low/ I'd blame autocorrect .. but I'm at my desk! Bruce > > Cheers, > > Bruce > > cc: Tom Zanussi <tom.zanussi@intel.com> > > The following changes since commit 21816355c00eadb2273d61b456f06239ca300b47: > > bitbake: cooker: fix handling of exceptions during exception handling (2012-09-10 13:14:08 +0100) > > are available in the git repository at: > git://git.pokylinux.org/poky-contrib zedd/kernel > http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel > > Bruce Ashfield (1): > linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates > > meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++++---- > meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 ++++++++-------- > 2 files changed, 12 insertions(+), 12 deletions(-) > > -- > 1.7.5.4 > > > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [PATCH 0/1] linux-yocto: 3.4 kernel updates 2012-09-10 18:11 [PATCH 0/1] linux-yocto: 3.4 kernel updates Bruce Ashfield 2012-09-10 18:11 ` [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates Bruce Ashfield 2012-09-10 18:14 ` [PATCH 0/1] linux-yocto: 3.4 kernel updates Bruce Ashfield @ 2012-09-12 17:26 ` Saul Wold 2 siblings, 0 replies; 17+ messages in thread From: Saul Wold @ 2012-09-12 17:26 UTC (permalink / raw) To: Bruce Ashfield; +Cc: openembedded-core On 09/10/2012 11:11 AM, Bruce Ashfield wrote: > Richard/Saul, > > Here's a small bump to 3.4.10 (32 commits) and an update to > pickup some configuration changes from TomZ (no impact on existing > features). All in all, it's a nice set of small fixes, with no risk. > > Cheers, > > Bruce > > cc: Tom Zanussi <tom.zanussi@intel.com> > > The following changes since commit 21816355c00eadb2273d61b456f06239ca300b47: > > bitbake: cooker: fix handling of exceptions during exception handling (2012-09-10 13:14:08 +0100) > > are available in the git repository at: > git://git.pokylinux.org/poky-contrib zedd/kernel > http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel > > Bruce Ashfield (1): > linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates > > meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++++---- > meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 ++++++++-------- > 2 files changed, 12 insertions(+), 12 deletions(-) > Merged into OE-Core Thanks Sau! ^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2012-09-12 17:38 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-09-10 18:11 [PATCH 0/1] linux-yocto: 3.4 kernel updates Bruce Ashfield
2012-09-10 18:11 ` [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates Bruce Ashfield
2012-09-11 4:50 ` Khem Raj
2012-09-11 4:52 ` Bruce Ashfield
2012-09-11 4:55 ` Khem Raj
2012-09-11 4:58 ` Bruce Ashfield
2012-09-11 5:16 ` Khem Raj
2012-09-11 5:17 ` Bruce Ashfield
2012-09-11 5:22 ` Khem Raj
2012-09-11 12:32 ` Bruce Ashfield
2012-09-11 6:59 ` Martin Jansa
[not found] ` <504F2F2E.3080507@windriver.com>
2012-09-11 12:37 ` Martin Jansa
2012-09-11 13:27 ` Bruce Ashfield
2012-09-11 13:33 ` Martin Jansa
2012-09-11 19:40 ` Bruce Ashfield
2012-09-10 18:14 ` [PATCH 0/1] linux-yocto: 3.4 kernel updates Bruce Ashfield
2012-09-12 17:26 ` Saul Wold
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox