Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] linux-yocto/3.4: v3.4.10 and uprobes/kprobes configuration updates
Date: Tue, 11 Sep 2012 00:52:21 -0400	[thread overview]
Message-ID: <504EC385.6060008@windriver.com> (raw)
In-Reply-To: <20120911045038.GE2980@sakrah.homelinux.org>

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
>




  reply	other threads:[~2012-09-11  5:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=504EC385.6060008@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox