From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] insane.bbclass: skip rdepends QA checks for kernel / modules
Date: Tue, 12 Jul 2011 15:22:26 +0100 [thread overview]
Message-ID: <1310480546.20015.1063.camel@rex> (raw)
In-Reply-To: <901d1d04284eaa806af61557f46bf35c07970b01.1310477287.git.paul.eggleton@linux.intel.com>
On Tue, 2011-07-12 at 14:29 +0100, Paul Eggleton wrote:
> The kernel and module recipes have very few dbg/dev packages, however
> they can easily have false positive results from the rdepends QA checks
> (e.g. kernel-module-lirc-dev). Thus disable these tests for any recipe
> that inherits kernel or module-base.
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
> meta/classes/insane.bbclass | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-07-12 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 13:29 [PATCH 0/1] kernel module QA warning fixes Paul Eggleton
2011-07-12 13:29 ` [PATCH 1/1] insane.bbclass: skip rdepends QA checks for kernel / modules Paul Eggleton
2011-07-12 14:22 ` Richard Purdie [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=1310480546.20015.1063.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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 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.