From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: Re: [PATCH 0/3] linux-yocto: kernel config updates
Date: Wed, 21 Sep 2011 23:56:07 -0400 [thread overview]
Message-ID: <4E7AB1D7.1040308@windriver.com> (raw)
In-Reply-To: <1316663623.13622.5.camel@ted>
On 11-09-21 11:53 PM, Richard Purdie wrote:
> On Wed, 2011-09-21 at 15:25 -0400, Bruce Ashfield wrote:
>> Richard/Saul,
>>
>> Here's another small series of kernel config updates from the linux-yocto
>> tree. During some build/boot and regression testing I noticed that some
>> configuration warnings weren't being dumped to a visible location. When
>> I moved all the warnings (patch 3/3) to the kernel audit phase, there were
>> some obvious clenaups to the configs to get us a clean audit.
>>
>> I've built and booted all the qemu machine. The net result here is
>> that we don't have any runtime config changes and we have met the clean
>> kernel configuration goal.
>>
>> The following changes since commit bcfff457f63f43f53bcaf04f116e09bb2bba9bd6:
>>
>> Fix mercurial fetcher in fetch2 (2011-09-21 14:07:31 +0100)
>>
>> are available in the git repository at:
>> git://git.pokylinux.org/poky-contrib zedd/kernel
>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>
>> Bruce Ashfield (3):
>> linux-yocto: simplify kernel configuration check expression
>> linux-yocto: add blktrace feature
>> linux-yocto: kernel configuration cleanups
>
> Merged to master. I'm a little worried we're still finding issues like
> this at this late stage :/.
Just housekeeping. They've been there for a while, and with the bigger
rocks to move I hadn't realized that the mapping to the kern-tools was
hiding output. We could have waited, but since the impact was nil on the
end result, I figured it was worth putting a good face forward for 1.1!
Cheers,
Bruce
>
> Cheers,
>
> Richard
>
prev parent reply other threads:[~2011-09-22 4:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 19:25 [PATCH 0/3] linux-yocto: kernel config updates Bruce Ashfield
2011-09-21 19:25 ` [PATCH 1/3] linux-yocto: simplify kernel configuration check expression Bruce Ashfield
2011-09-21 19:25 ` [PATCH 2/3] linux-yocto: add blktrace feature Bruce Ashfield
2011-09-21 19:25 ` [PATCH 3/3] linux-yocto: kernel configuration cleanups Bruce Ashfield
2011-09-22 3:53 ` [PATCH 0/3] linux-yocto: kernel config updates Richard Purdie
2011-09-22 3:56 ` 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=4E7AB1D7.1040308@windriver.com \
--to=bruce.ashfield@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox