From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: alexander.kanavin@linux.intel.com,
Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: saul.wold@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] linux-yocto: -stable and BSP updates
Date: Fri, 12 Feb 2016 11:28:22 +0000 [thread overview]
Message-ID: <1455276502.16142.272.camel@linuxfoundation.org> (raw)
In-Reply-To: <61992.10.252.9.169.1455277045.squirrel@linux.intel.com>
On Fri, 2016-02-12 at 13:37 +0200, alexander.kanavin@linux.intel.com
wrote:
> > Here are the pending updates to the 4.1 and 4.4 kerne to integrate
> > -stable
> > updates
> > and to backport the mainline galileo support patches.
> > Bruce Ashfield (3):
> > linux-yocto/4.4: update to v4.4.1
> > linux-yocto/4.1: update to v4.1.17
> > linux-yocto/4.1: galileo backports and support
>
> Shouldn't linux-libc-headers be updated to 4.4.1 at the same time?
We tend to only change linux-libc-headers if there is a need to outside
major version bumps. We have had cases where there have been fixes in
point releases we've needed but they should be rare.
Cheers,
Richard
next prev parent reply other threads:[~2016-02-12 11:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 15:08 [PATCH 0/3] linux-yocto: -stable and BSP updates Bruce Ashfield
2016-02-11 15:08 ` [PATCH 1/3] linux-yocto/4.4: update to v4.4.1 Bruce Ashfield
2016-02-11 15:08 ` [PATCH 2/3] linux-yocto/4.1: update to v4.1.17 Bruce Ashfield
2016-02-11 15:08 ` [PATCH 3/3] linux-yocto/4.1: galileo backports and support Bruce Ashfield
2016-02-12 11:37 ` [PATCH 0/3] linux-yocto: -stable and BSP updates alexander.kanavin
2016-02-12 11:28 ` Richard Purdie [this message]
2016-02-12 16:06 ` Bruce Ashfield
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=1455276502.16142.272.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.com \
/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