From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Fix building initramfs kernel with appended dtb
Date: Wed, 31 Jul 2013 17:04:28 +0200 [thread overview]
Message-ID: <20130731170428.102c93a4@skate> (raw)
In-Reply-To: <1375281113-18893-1-git-send-email-nford@westpond.com>
Dear Nathan Ford,
Humm, yes, maybe, but would it be possible to get a slightly more
verbose commit log that explains what is the problem and how you're
fixing it?
Thanks!
On Wed, 31 Jul 2013 10:31:53 -0400, Nathan Ford wrote:
>
> Signed-off-by: Nathan Ford <nford@westpond.com>
> ---
> linux/linux.mk | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/linux/linux.mk b/linux/linux.mk
> index 17e9838..9d29d9d 100644
> --- a/linux/linux.mk
> +++ b/linux/linux.mk
> @@ -311,7 +311,8 @@ endif
> $(LINUX_DIR)/.stamp_initramfs_rebuilt: $(LINUX_DIR)/.stamp_target_installed $(LINUX_DIR)/.stamp_images_installed $(BINARIES_DIR)/rootfs.cpio
> @$(call MESSAGE,"Rebuilding kernel with initramfs")
> # Build the kernel.
> - $(TARGET_MAKE_ENV) $(MAKE) $(LINUX_MAKE_FLAGS) -C $(@D) $(LINUX_IMAGE_NAME)
> + $(TARGET_MAKE_ENV) $(MAKE) $(LINUX_MAKE_FLAGS) -C $(@D) $(LINUX_IMAGE_TARGET)
> + $(LINUX_APPEND_DTB)
> # Copy the kernel image to its final destination
> cp $(LINUX_IMAGE_PATH) $(BINARIES_DIR)
> # If there is a .ub file copy it to the final destination
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-07-31 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 14:31 [Buildroot] [PATCH] Fix building initramfs kernel with appended dtb Nathan Ford
2013-07-31 15:04 ` Thomas Petazzoni [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=20130731170428.102c93a4@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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