public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: boot: Fix usage of kecho
Date: Mon, 12 Nov 2012 22:24:22 +0000	[thread overview]
Message-ID: <201211122224.22513.arnd@arndb.de> (raw)
In-Reply-To: <CAOMZO5BEi7n76roOAgBFEqvqJybsCeGKZuozqYL5PRL3hJnghQ@mail.gmail.com>

On Monday 12 November 2012, Fabio Estevam wrote:
> >> > From: Fabio Estevam <fabio.estevam@freescale•com>
> >> >
> >> > Since commit edc88ceb0 (ARM: be really quiet when building with 'make -s') the
> >> > following output is generated when building a kernel for ARM:
> >> >
> >> > echo '  Kernel: arch/arm/boot/Image is ready'
> >> >   Kernel: arch/arm/boot/Image is ready
> >> >   Building modules, stage 2.
> >> > echo '  Kernel: arch/arm/boot/zImage is ready'
> >> >   Kernel: arch/arm/boot/zImage is ready
> >> >
> >> > As per Documentation/kbuild/makefiles.txt the correct way of using kecho is
> >> > '@$(kecho)'.
> >> >
> >> > Make this change so no more unwanted 'echo' messages are displayed.
> >> >
> >> > Signed-off-by: Fabio Estevam <fabio.estevam@freescale•com>
> >>
> >> Acked-by: Nicolas Pitre <nico@linaro•org>
> >
> > Acked-by: Arnd Bergmann <arnd@arndb•de>
> 
> Would this one go via arm-soc tree?

The correct way would be via Russell's tree, but since we're sending bug fix
patches tomorrow through arm-soc and this one is getting embarrassingly old,
I've applied it now.

Thanks for the reminder.

	Arnd

      reply	other threads:[~2012-11-12 22:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 18:37 [PATCH] ARM: boot: Fix usage of kecho Fabio Estevam
2012-10-24 18:45 ` Nicolas Pitre
2012-10-24 19:28   ` Arnd Bergmann
2012-11-12 22:09     ` Fabio Estevam
2012-11-12 22:24       ` Arnd Bergmann [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=201211122224.22513.arnd@arndb.de \
    --to=arnd@arndb$(echo .)de \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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