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:58:27 -0400	[thread overview]
Message-ID: <504EC4F3.30705@windriver.com> (raw)
In-Reply-To: <20120911045557.GF2980@sakrah.homelinux.org>

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





  reply	other threads:[~2012-09-11  5:11 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
2012-09-11  4:55       ` Khem Raj
2012-09-11  4:58         ` Bruce Ashfield [this message]
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=504EC4F3.30705@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