From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] objdump: restore quiet build output
Date: Mon, 16 Sep 2019 14:18:36 -0500 [thread overview]
Message-ID: <20190916191836.4jwbndzivivejftg@treble> (raw)
In-Reply-To: <20190910092031.2897823-1-arnd@arndb.de>
On Tue, Sep 10, 2019 at 11:20:24AM +0200, Arnd Bergmann wrote:
> After a recent sync-check.sh update, a 'make -s' build prints a
> single line of output from the 'cd -' command:
>
> /git/linux/tools/objtool
>
> This is clearly unintended, so revert back to a completely quiet
> build by redirecting the cd output to /dev/null.
>
> Fixes: 2ffd84ae973b ("objtool: Update sync-check.sh from perf's check-headers.sh")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> tools/objtool/sync-check.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/objtool/sync-check.sh b/tools/objtool/sync-check.sh
> index 0a832e265a50..94b8d76c2851 100755
> --- a/tools/objtool/sync-check.sh
> +++ b/tools/objtool/sync-check.sh
> @@ -48,4 +48,4 @@ check arch/x86/include/asm/insn.h '-I "^#include [\"<]\(asm/\)*inat.h[\">]"'
> check arch/x86/lib/inat.c '-I "^#include [\"<]\(../include/\)*asm/insn.h[\">]"'
> check arch/x86/lib/insn.c '-I "^#include [\"<]\(../include/\)*asm/in\(at\|sn\).h[\">]"'
>
> -cd -
> +cd - > /dev/null
> --
> 2.20.0
>
Arnaldo, do you want to pick this one up?
Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
--
Josh
prev parent reply other threads:[~2019-09-16 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 9:20 [PATCH] objdump: restore quiet build output Arnd Bergmann
2019-09-16 19:18 ` Josh Poimboeuf [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=20190916191836.4jwbndzivivejftg@treble \
--to=jpoimboe@redhat.com \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=arnd@arndb.de \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).