From: Mike Crowe <mac@mcrowe.com>
To: openembedded-core@lists.openembedded.org
Cc: Mike Crowe <mcrowe@brightsign.biz>, Mike Crowe <mac@mcrowe.com>
Subject: [PATCH 1/2] Revert "kernel.bbclass: move bundle_initramfs after kernel_link_vmlinux"
Date: Fri, 22 Nov 2013 14:04:18 +0000 [thread overview]
Message-ID: <1385129059-941-2-git-send-email-mac@mcrowe.com> (raw)
In-Reply-To: <1385129059-941-1-git-send-email-mac@mcrowe.com>
This reverts commit 3baa63b4d588c3262254528b406ede265dd117bf. It broke
builds that aren't using kernel-yocto.
Signed-off-by: Mike Crowe <mcrowe@brightsign.biz>
---
meta/classes/kernel.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 48999fe..ba13e67 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -152,7 +152,7 @@ python do_devshell_prepend () {
os.environ["LDFLAGS"] = ''
}
-addtask bundle_initramfs after do_kernel_link_vmlinux before do_build
+addtask bundle_initramfs after do_compile before do_build
kernel_do_compile() {
unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS MACHINE
--
1.7.10.4
next prev parent reply other threads:[~2013-11-22 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 14:04 kernel.bbclass: Fix various bundle_initramfs problems Mike Crowe
2013-11-22 14:04 ` Mike Crowe [this message]
2013-11-22 15:53 ` [PATCH 1/2] Revert "kernel.bbclass: move bundle_initramfs after kernel_link_vmlinux" Bruce Ashfield
2013-11-22 15:54 ` Bruce Ashfield
2013-11-22 14:04 ` [PATCH 2/2] kernel.bbclass: Stop bundle_initramfs thwarting sstate cache and fix race Mike Crowe
2013-11-22 14:23 ` kernel.bbclass: Fix various bundle_initramfs problems (v2) Mike Crowe
2013-11-22 14:23 ` [PATCH 1/2] Revert "kernel.bbclass: move bundle_initramfs after kernel_link_vmlinux" Mike Crowe
2013-11-22 14:23 ` [PATCH 2/2] kernel.bbclass: Stop bundle_initramfs thwarting sstate cache and fix race Mike Crowe
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=1385129059-941-2-git-send-email-mac@mcrowe.com \
--to=mac@mcrowe.com \
--cc=mcrowe@brightsign.biz \
--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.