From: Roland Stigge <stigge@antcom.de>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Kernel build ignores missing mkimage on building uImage
Date: Fri, 07 Jan 2011 00:28:34 +0100 [thread overview]
Message-ID: <4D265022.5020700@antcom.de> (raw)
In-Reply-To: <20110106135558.GC1841@sepie.suse.cz>
Hi,
On 06/01/11 14:55, Michal Marek wrote:
>> I.e. it says: "uImage is ready" even though the uImage file doesn't
>> exist because mkimage is missing.
>>
>> (I'm working with Linux' current mainline GIT and also see that the
>> problem is also present in the mmarek repo on git.kernel.org.)
>>
>> I propose the attached patch.
>>
>> Thanks for considering.
>
> The patch makes sense and afaics none of the architectures relies on
> this behaviour (either they can't work without mkimage, or a
> uimage-style target has to be requested by the user). Can I assume
> "Signed-off-by: Roland Stigge <stigge@antcom.de>" on this patch.
Yes!
Thanks,
Roland
prev parent reply other threads:[~2011-01-06 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 16:19 Kernel build ignores missing mkimage on building uImage Roland Stigge
2011-01-06 13:55 ` Michal Marek
2011-01-06 23:28 ` Roland Stigge [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=4D265022.5020700@antcom.de \
--to=stigge@antcom.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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