All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Subject: [PATCH 0/2] Fix log_check warnings for bb* logging functions
Date: Tue, 13 Dec 2016 11:05:04 +1300	[thread overview]
Message-ID: <cover.1481579713.git.paul.eggleton@linux.intel.com> (raw)

This patchset requires the patch I just sent to the bitbake-devel mailing
list ("lib/bb/build: enable access to logger within tasks").


The following changes since commit d62f18c39bc0ed3b0f5ac8465b393c15f2143ecf:

  targetloader.py: drop test for ClassType (2016-12-12 15:16:39 +0000)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/rootfs-log-check-oe
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/rootfs-log-check-oe

Paul Eggleton (2):
  lib/oe/rootfs: fix log_check warnings being printed twice with RPM packaging
  classes/image: suppress log_check mechanism for warnings/errors logged through BitBake

 meta/classes/image.bbclass | 10 +++++++++-
 meta/lib/oe/rootfs.py      | 31 ++++++++++++++++---------------
 2 files changed, 25 insertions(+), 16 deletions(-)

-- 
2.5.5



             reply	other threads:[~2016-12-12 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 22:05 Paul Eggleton [this message]
2016-12-12 22:05 ` [PATCH 1/2] lib/oe/rootfs: fix log_check warnings being printed twice with RPM packaging Paul Eggleton
2016-12-12 22:05 ` [PATCH 2/2] classes/image: suppress log_check mechanism for warnings/errors logged through BitBake Paul Eggleton

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.1481579713.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.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 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.