From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Saul Wold <saul.wold@intel.com>
Subject: Re: [PATCH 0/3] linux-yocto: -stable and BSP updates
Date: Fri, 12 Feb 2016 11:06:07 -0500 [thread overview]
Message-ID: <CADkTA4N0UG+OR_7nBkq1_1U05j=OxYtrLvo9eCum2CxnXD12Vg@mail.gmail.com> (raw)
In-Reply-To: <1455276502.16142.272.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
On Fri, Feb 12, 2016 at 6:28 AM, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
> 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.
>
Absolutely, and in this case, I didn't see anything compelling in 4.4.1
that
would warrant an update. So I've left things as-is. I look at each point
upgrade
with that in mind.
Cheers,
Bruce
>
> Cheers,
>
> Richard
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
[-- Attachment #2: Type: text/html, Size: 2354 bytes --]
prev parent reply other threads:[~2016-02-12 16:06 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
2016-02-12 16:06 ` Bruce Ashfield [this message]
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='CADkTA4N0UG+OR_7nBkq1_1U05j=OxYtrLvo9eCum2CxnXD12Vg@mail.gmail.com' \
--to=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.