From: Darren Hart <dvhart@linux.intel.com>
To: Saul Wold <saul.wold@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] linux-yocto: update 3.2 kernel to v3.2.7
Date: Mon, 27 Feb 2012 16:02:24 -0800 [thread overview]
Message-ID: <4F4C1990.9090903@linux.intel.com> (raw)
In-Reply-To: <4F4C1077.3030106@intel.com>
On 02/27/2012 03:23 PM, Saul Wold wrote:
> On 02/27/2012 11:34 AM, Bruce Ashfield wrote:
>> Updating the 3.2 kernel recipe to the latest -stable release.
>>
>> Signed-off-by: Bruce Ashfield<bruce.ashfield@windriver.com>
>> ---
>> meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb | 9 +++++----
>> meta/recipes-kernel/linux/linux-yocto_3.2.bb | 19 ++++++++++---------
>> 2 files changed, 15 insertions(+), 13 deletions(-)
>>
>
> I noticed that there are 3 Packaging WARNINGS in this build, we are
> trying to improve the overall Quality by reducing the warnings. These
> are probably general to all linux-yocto recipes.
>
> Can you address these:
>
> WARNING: For recipe linux-yocto, the following files/directories were
> installed but not shipped in any package:
> WARNING: /lib/modules/3.2.2-yocto-standard+/build
> WARNING: /lib/modules/3.2.2-yocto-standard+/source
> WARNING: /etc/modprobe.d
>
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2036
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-02-28 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 19:34 [PATCH 0/3] linux-yocto: consolidated pull request Bruce Ashfield
2012-02-27 19:34 ` [PATCH 1/3] linux-yocto: update 3.0 kernel to v3.0.22 Bruce Ashfield
2012-02-27 19:34 ` [PATCH 2/3] linux-yocto: update 3.2 kernel to v3.2.7 Bruce Ashfield
2012-02-27 23:23 ` Saul Wold
2012-02-28 0:02 ` Darren Hart [this message]
2012-02-27 19:34 ` [PATCH 3/3] linux-yocto: allow non-branched repositories to check out Bruce Ashfield
2012-02-28 18:41 ` [PATCH 0/3] linux-yocto: consolidated pull request 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=4F4C1990.9090903@linux.intel.com \
--to=dvhart@linux.intel.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