From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: add boot image dependencies to not generate invalid images
Date: Tue, 18 Aug 2015 11:44:58 +0100 [thread overview]
Message-ID: <20150818104458.GO7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1439049211-4181-1-git-send-email-yamada.masahiro@socionext.com>
On Sun, Aug 09, 2015 at 12:53:31AM +0900, Masahiro Yamada wrote:
> U-Boot is often used to boot the kernel on ARM boards, but uImage
> is not built by "make all", so we are often inclined to do
> "make all uImage" to generate DTBs, modules and uImage in a single
> command, but we should notice a pitfall behind it. In fact,
> "make all uImage" could generate an invalid uImage if it is run with
> the parallel option (-j).
Please put this patch in the patch system. Thanks.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-08-18 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 15:53 [PATCH v2] ARM: add boot image dependencies to not generate invalid images Masahiro Yamada
2015-08-18 10:44 ` Russell King - ARM Linux [this message]
2015-08-18 10:54 ` Masahiro Yamada
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=20150818104458.GO7557@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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