From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH 2/2] ARM: delete "*Image is ready" log
Date: Thu, 31 Mar 2016 17:53:01 +0100 [thread overview]
Message-ID: <20160331165301.GM19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1459442582-23121-2-git-send-email-yamada.masahiro@socionext.com>
On Fri, Apr 01, 2016 at 01:43:02AM +0900, Masahiro Yamada wrote:
> Commit 3939f3345050 ("ARM: 8418/1: add boot image dependencies to not
> generate invalid images") fixed bad image generation in case of
> parallel building, but as a side effect, Kbuild now descends into
> arch/arm/boot/ again and again, duplicating the same log messages.
> This is clumsy.
>
> In the example below (incremental build),
> "Kernel: arch/arm/boot/Image is ready" is displayed three times.
> "Kernel: arch/arm/boot/zImage is ready" is displayed twice.
I disagree. Image and zImage are the final targets that users are
interested in, we should tell people that they've been successfully
created.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: delete "*Image is ready" log
Date: Thu, 31 Mar 2016 17:53:01 +0100 [thread overview]
Message-ID: <20160331165301.GM19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1459442582-23121-2-git-send-email-yamada.masahiro@socionext.com>
On Fri, Apr 01, 2016 at 01:43:02AM +0900, Masahiro Yamada wrote:
> Commit 3939f3345050 ("ARM: 8418/1: add boot image dependencies to not
> generate invalid images") fixed bad image generation in case of
> parallel building, but as a side effect, Kbuild now descends into
> arch/arm/boot/ again and again, duplicating the same log messages.
> This is clumsy.
>
> In the example below (incremental build),
> "Kernel: arch/arm/boot/Image is ready" is displayed three times.
> "Kernel: arch/arm/boot/zImage is ready" is displayed twice.
I disagree. Image and zImage are the final targets that users are
interested in, we should tell people that they've been successfully
created.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-03-31 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 16:43 [PATCH 1/2] ARM: specify install, zinstall, uinstall as PHONY targets Masahiro Yamada
2016-03-31 16:43 ` Masahiro Yamada
2016-03-31 16:43 ` [PATCH 2/2] ARM: delete "*Image is ready" log Masahiro Yamada
2016-03-31 16:43 ` Masahiro Yamada
2016-03-31 16:53 ` Russell King - ARM Linux [this message]
2016-03-31 16:53 ` Russell King - ARM Linux
2016-04-01 2:55 ` Masahiro Yamada
2016-04-01 2:55 ` 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=20160331165301.GM19428@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=yamada.masahiro@socionext.com \
/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.