From: Michal Simek <monstr@monstr.eu>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/7] microblaze: move "... is ready" message to arch/microblaze/Makefile
Date: Wed, 5 Dec 2018 16:47:58 +0100 [thread overview]
Message-ID: <35d05327-e500-2f1a-a8d2-e1683ce190f2@monstr.eu> (raw)
In-Reply-To: <1543823457-32478-4-git-send-email-yamada.masahiro@socionext.com>
[-- Attachment #1.1: Type: text/plain, Size: 2541 bytes --]
On 03. 12. 18 8:50, Masahiro Yamada wrote:
> To prepare for more fixes, move this to arch/microblaze/Makefile.
> Otherwise, the same "... is ready" would be printed multiple times.
>
> (Another solution would be, to remove these messages entirely unless
> people persist with them.)
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> arch/microblaze/Makefile | 2 ++
> arch/microblaze/boot/Makefile | 4 ----
> 2 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/arch/microblaze/Makefile b/arch/microblaze/Makefile
> index 97e1384..cfd7bfca 100644
> --- a/arch/microblaze/Makefile
> +++ b/arch/microblaze/Makefile
> @@ -81,9 +81,11 @@ archclean:
>
> linux.bin linux.bin.gz linux.bin.ub: vmlinux
> $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
> + @echo 'Kernel: $(boot)/$@ is ready' ' (#'`cat .version`')'
>
> simpleImage.%: vmlinux
> $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
> + @echo 'Kernel: $(boot)/$@ is ready' ' (#'`cat .version`')'
>
> define archhelp
> echo '* linux.bin - Create raw binary'
> diff --git a/arch/microblaze/boot/Makefile b/arch/microblaze/boot/Makefile
> index e8684a2..c2579a7 100644
> --- a/arch/microblaze/boot/Makefile
> +++ b/arch/microblaze/boot/Makefile
> @@ -9,15 +9,12 @@ OBJCOPYFLAGS := -R .note -R .comment -R .note.gnu.build-id -O binary
>
> $(obj)/linux.bin: vmlinux FORCE
> $(call if_changed,objcopy)
> - @echo 'Kernel: $@ is ready' ' (#'`cat .version`')'
>
> $(obj)/linux.bin.ub: $(obj)/linux.bin FORCE
> $(call if_changed,uimage)
> - @echo 'Kernel: $@ is ready' ' (#'`cat .version`')'
>
> $(obj)/linux.bin.gz: $(obj)/linux.bin FORCE
> $(call if_changed,gzip)
> - @echo 'Kernel: $@ is ready' ' (#'`cat .version`')'
>
> quiet_cmd_cp = CP $< $@$2
> cmd_cp = cat $< >$@$2 || (rm -f $@ && echo false)
> @@ -35,6 +32,5 @@ $(obj)/simpleImage.%: vmlinux FORCE
> $(call if_changed,objcopy)
> $(call if_changed,uimage)
> $(call if_changed,strip,.strip)
> - @echo 'Kernel: $(UIMAGE_OUT) is ready' ' (#'`cat .version`')'
>
> clean-files += simpleImage.*
>
TBH I can't see this problematic but if this is aligned with others I
have no problem with it.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2018-12-05 15:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 7:50 [PATCH 0/7] microblaze: fix various problems in building boot images Masahiro Yamada
2018-12-03 7:50 ` [PATCH 1/7] microblaze: fix cleaning of " Masahiro Yamada
2018-12-05 15:41 ` Michal Simek
2018-12-03 7:50 ` [PATCH 2/7] microblaze: adjust the help to the real behavior Masahiro Yamada
2018-12-05 15:40 ` Michal Simek
2018-12-06 5:27 ` Masahiro Yamada
2018-12-06 12:52 ` Michal Simek
2018-12-07 9:50 ` Masahiro Yamada
2018-12-07 10:21 ` Masahiro Yamada
2018-12-07 10:47 ` Michal Simek
2018-12-03 7:50 ` [PATCH 3/7] microblaze: move "... is ready" message to arch/microblaze/Makefile Masahiro Yamada
2018-12-05 15:47 ` Michal Simek [this message]
2018-12-03 7:50 ` [PATCH 4/7] microblaze: fix multiple bugs in arch/microblaze/boot/Makefile Masahiro Yamada
2018-12-05 15:57 ` Michal Simek
2018-12-03 7:50 ` [PATCH 5/7] microblaze: add linux.bin* and simpleImage.* to PHONY Masahiro Yamada
2018-12-05 15:59 ` Michal Simek
2018-12-03 7:50 ` [PATCH 6/7] microblaze: fix race condition in building boot images Masahiro Yamada
2018-12-05 16:31 ` Michal Simek
2018-12-08 6:51 ` Masahiro Yamada
2018-12-03 7:50 ` [PATCH 7/7] microblaze: remove the unneeded code just in case file copy fails Masahiro Yamada
2018-12-05 16:33 ` Michal Simek
2018-12-05 16:41 ` [PATCH 0/7] microblaze: fix various problems in building boot images Michal Simek
2018-12-06 5:08 ` Masahiro Yamada
2018-12-06 13:09 ` Michal Simek
2018-12-07 11:25 ` Masahiro Yamada
2018-12-06 14:44 ` Michal Simek
2018-12-07 11:29 ` Masahiro Yamada
2018-12-07 13:29 ` Michal Simek
2018-12-07 15:19 ` Michal Simek
2018-12-08 6:14 ` Masahiro Yamada
2018-12-12 13:50 ` Michal Simek
2018-12-12 14:11 ` Masahiro Yamada
2018-12-12 14:21 ` 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=35d05327-e500-2f1a-a8d2-e1683ce190f2@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox