From: Arnd Bergmann <arnd@arndb.de>
To: Michal Marek <mmarek@suse.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lz4c: shut up lz4c output
Date: Mon, 29 Feb 2016 15:35:09 +0100 [thread overview]
Message-ID: <2781274.5SXPMrqOdg@wuerfel> (raw)
In-Reply-To: <56D44065.4070005@suse.com>
On Monday 29 February 2016 13:58:13 Michal Marek wrote:
> On 2016-02-29 13:40, Arnd Bergmann wrote:
> > When KERNEL_LZ4 is set, we always get an output even when building
> > with 'make -s':
> >
> > *** LZ4 Compression CLI , by Yann Collet (May 31 2013) ***
> > ! Generating compressed LZ4 using Legacy format (deprecated !) !
> > Using stdin for input
> > Using stdout for output
> > Compressed 11213376 bytes into 4555781 bytes ==> 40.63%
> > Done in 0.63 s ==> 16.97 MB/s
> >
> > The output is not helpful in the context of building the kernel,
> > so this patch hides the stdout output of the lz4 binary completely.
>
> > - lz4c -l -c1 stdin stdout && $(call size_append, $(filter-out FORCE,$^))) > $@ || \
> > + lz4c -l -c1 stdin stdout && $(call size_append, $(filter-out FORCE,$^))) > $@ 2>&1 || \
> > (rm -f $@ ; false)
>
> Hi Arnd,
>
> this redirection does not hide it, but rather includes it in the
> compressed image file.
Oops, you are right. I was cleaning out some older patches I had in my
queue and hadn't realized it was completely botched this way.
> BTW, my copy of lz4c only displays this warning with -v.
I've updated my copy of lz4c now and can confirm that the output
is completely gone (without -v). I won't follow up with a fixed version
then, as the problem is already solved elsewhere.
Arnd
prev parent reply other threads:[~2016-02-29 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 12:40 [PATCH] lz4c: shut up lz4c output Arnd Bergmann
2016-02-29 12:58 ` Michal Marek
2016-02-29 14:35 ` 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=2781274.5SXPMrqOdg@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.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