From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/5] linux-yocto: consolidated pull request
Date: Wed, 25 Mar 2015 09:26:25 +0000 [thread overview]
Message-ID: <1427275585.14020.39.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1427222980.git.bruce.ashfield@windriver.com>
On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
> Hi all,
>
> Here is the latest linux-yocto consolidated pull request. It is a mix of
> kernel version -stable imports (CVEs and fixes), kernel configuration
> changes, a documentation update and kernel configuration enhancement.
>
> The -stable updates are routine, and I build/boot tested them here
> (with my fixup commits being evidence). These are ready for a round of
> autobuilder/soak testing.
Something in here broke lttng-modules causing cascades of failures on
the autobuilder so I've updated it to the latest code on the 2.6 stable
branch and am retesting.
Cheers,
Richard
next prev parent reply other threads:[~2015-03-25 9:26 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 18:57 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2015-03-24 18:57 ` [PATCH 1/5] kernel-yocto: allow in-tree defconfigs Bruce Ashfield
2015-03-24 18:57 ` [PATCH 2/5] linux-yocto/3.19: configuration updates and stable import Bruce Ashfield
2015-03-24 18:57 ` [PATCH 3/5] linux-yocto/3.14: integrate korg stable and meta data changes Bruce Ashfield
2015-03-24 18:57 ` [PATCH 4/5] linux-yocto/3.19: fixes for Intel core warnings Bruce Ashfield
2015-04-13 23:11 ` Martin Jansa
2015-03-24 18:57 ` [PATCH 5/5] skeleton: clarify linux-yocto-custom workflow Bruce Ashfield
2015-03-25 9:26 ` Richard Purdie [this message]
2015-03-25 12:13 ` [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2015-03-25 13:26 ` Bruce Ashfield
2015-03-25 13:52 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2024-08-11 18:04 bruce.ashfield
2024-08-12 9:47 ` Richard Purdie
2024-08-12 12:47 ` Bruce Ashfield
2023-02-01 16:28 bruce.ashfield
2020-11-19 19:17 Bruce Ashfield
2020-05-29 1:29 Bruce Ashfield
2020-05-03 15:44 Bruce Ashfield
2020-05-04 8:30 ` Richard Purdie
2020-05-04 12:56 ` Bruce Ashfield
2020-03-24 23:04 Bruce Ashfield
2016-07-27 16:57 Bruce Ashfield
2016-06-21 15:20 Bruce Ashfield
2016-04-13 16:12 Bruce Ashfield
2015-05-01 1:34 Bruce Ashfield
2015-05-01 22:59 ` Richard Purdie
2015-05-01 23:30 ` Bruce Ashfield
2015-05-02 8:13 ` Martin Jansa
2015-05-03 2:50 ` Bruce Ashfield
2015-05-06 14:42 ` Martin Jansa
2015-05-06 14:58 ` Bruce Ashfield
2015-05-06 15:33 ` Martin Jansa
2015-05-06 15:44 ` Richard Purdie
2015-05-06 16:07 ` Martin Jansa
2015-05-06 17:46 ` Bruce Ashfield
2015-05-06 21:32 ` Richard Purdie
2015-05-06 22:49 ` Martin Jansa
2015-05-07 15:33 ` Bruce Ashfield
2015-05-07 6:33 ` Khem Raj
2015-05-02 9:00 ` Richard Purdie
2015-05-03 2:53 ` Bruce Ashfield
2015-05-03 3:52 ` Bruce Ashfield
2015-05-03 10:48 ` Richard Purdie
2015-05-03 21:30 ` Richard Purdie
2015-05-04 4:36 ` Bruce Ashfield
2015-05-04 15:01 ` Bruce Ashfield
2013-08-23 18:08 Bruce Ashfield
2013-08-23 21:30 ` Bruce Ashfield
2013-08-24 6:33 ` Saul Wold
2013-08-24 13:34 ` Bruce Ashfield
2013-08-24 13:45 ` Bruce Ashfield
2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
2013-08-24 14:47 ` Bruce Ashfield
2013-08-24 14:59 ` Bruce Ashfield
2013-08-24 16:05 ` Bruce Ashfield
2012-02-05 6:31 Bruce Ashfield
2012-02-08 4:09 ` Saul Wold
2012-01-11 18:52 Bruce Ashfield
2012-01-17 19:28 ` 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=1427275585.14020.39.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.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