From: Darren Hart <dvhart@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Darren Hart <dvhart@linux.intel.com>
Subject: [PATCH 0/2] kernel.bbclass fix and cleanup
Date: Tue, 19 Apr 2011 8:11:35 -0700 [thread overview]
Message-ID: <cover.1303170477.git.dvhart@linux.intel.com> (raw)
From: Darren Hart <dvhart@linux.intel.com>
The following commit introduced a build bug and left some debug lying around.
commit 3b49416fc7a7ee9bfe722f2e6089aa18df41dc58
Author: Darren Hart <dvhart@linux.intel.com>
Date: Tue Mar 8 17:09:10 2011 -0800
kernel/bbclass: rework kernel and module classes to allow for building
out-of-tree modules
The following 2 patches address that.
Thanks,
Darren Hart <dvhart@linux.intel.com>
---
Darren Hart (2):
kernel: Copy over bzImage to sysroots during install
kernel: Remove debug statements
meta/classes/kernel.bbclass | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
--
1.7.3.4
next reply other threads:[~2011-04-19 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 15:11 Darren Hart [this message]
2011-04-19 15:11 ` [PATCH 2/2] kernel: Remove debug statements Darren Hart
2011-04-19 15:11 ` [PATCH 1/2] kernel: Copy over bzImage to sysroots during install Darren Hart
2011-04-19 22:36 ` [PATCH 0/2] kernel.bbclass fix and cleanup 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.1303170477.git.dvhart@linux.intel.com \
--to=dvhart@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