Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] QA warning fixes
Date: Thu,  7 Jul 2011 18:32:45 +0100	[thread overview]
Message-ID: <cover.1310059749.git.paul.eggleton@linux.intel.com> (raw)

I found a couple of issues with the recent insane.bbclass changes. The
following patches fix them as well as add a warning fix for something I
noticed when building a kernel with LIRC support.

The following changes since commit f1fc6d084b079dea21ff1a30b815496452042490:

  pulseaudio: add 0.9.23 (2011-07-07 13:44:36 +0100)

are available in the git repository at:
  git://git.openembedded.org/openembedded-core-contrib paule/qa-dev-deps
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/qa-dev-deps

Paul Eggleton (3):
  insane.bbclass: allow dev-deps to be skipped via INSANE_SKIP
  insane.bbclass: fix error/warning status being inverted
  kernel.bbclass: prevent QA warning about kernel-module-lirc-dev

 meta/classes/insane.bbclass |    6 +++---
 meta/classes/kernel.bbclass |    4 ++++
 2 files changed, 7 insertions(+), 3 deletions(-)

-- 
1.7.4.1




             reply	other threads:[~2011-07-07 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 17:32 Paul Eggleton [this message]
2011-07-07 17:32 ` [PATCH 1/3] insane.bbclass: allow dev-deps to be skipped via INSANE_SKIP Paul Eggleton
2011-07-07 17:32 ` [PATCH 2/3] insane.bbclass: fix error/warning status being inverted Paul Eggleton
2011-07-07 17:32 ` [PATCH 3/3] kernel.bbclass: prevent QA warning about kernel-module-lirc-dev Paul Eggleton
2011-07-07 19:08   ` Andreas Mueller
2011-07-07 19:13     ` Phil Blundell
2011-07-08 16:34 ` [PATCH 0/3] QA warning fixes Richard Purdie

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=cover.1310059749.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.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