From: David Howells <dhowells@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: dhowells@redhat.com, David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org,
linux-kbuild@vger.kernel.org, Michal Marek <mmarek@suse.com>,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] modsign: hide openssl output in silent builds
Date: Fri, 26 Feb 2016 11:20:28 +0000 [thread overview]
Message-ID: <7539.1456485628@warthog.procyon.org.uk> (raw)
In-Reply-To: <1456417901-2192433-1-git-send-email-arnd@arndb.de>
Arnd Bergmann <arnd@arndb.de> wrote:
> When a user calls 'make -s', we can assume they don't want to
> see any output except for warnings and errors, but instead
> they see this for a warning free build:
>
> ###
> ### Now generating an X.509 key pair to be used for signing modules.
> ###
> ### If this takes a long time, you might wish to run rngd in the
> ### background to keep the supply of entropy topped up. It
> ### needs to be run as root, and uses a hardware random
> ### number generator if one is available.
> ###
> Generating a 4096 bit RSA private key
> .................................................................................................................................................................................................................................++
> ..............................................................................................................................++
> writing new private key to 'certs/signing_key.pem'
> -----
> ###
> ### Key pair generated.
> ###
>
> The output can confuse simple build testing scripts that just check
> for an empty build log.
>
> This patch silences all the output:
> - "echo" is changed to "@$(kecho)", which is dropped when "-s" gets
> passed
> - the openssl command itself is only printed with V=1, using the
> $(Q) macro
> - The output of openssl gets redircted to /dev/null on "-s" builds.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied.
David
prev parent reply other threads:[~2016-02-26 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 16:31 [PATCH] modsign: hide openssl output in silent builds Arnd Bergmann
2016-02-26 11:20 ` David Howells [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=7539.1456485628@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=arnd@arndb.de \
--cc=dwmw2@infradead.org \
--cc=keyrings@vger.kernel.org \
--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