linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] x86: use stdout for success and stdout for failure
Date: Tue, 25 Oct 2016 22:56:03 +0200	[thread overview]
Message-ID: <1477428965-20548-1-git-send-email-pebolle@tiscali.nl> (raw)

For some time now my x86 builds are warning free. Yay! But there's still one
single line printed to stderr:
    Succeed: decoded and checked 1767380 instructions

This message is printed if the "insn decoder test" ran successful. Patch 1/2
sends this message to stdout (and fixes the typo).

Patch 2/2 does the reverse for the "insn sanity test": it sends a message to
stderr if that test fails.

One thing puzzles me about these two tests: I must have run them hundreds of
times but I've never seen them fail. Have other people ran into failures?

Paul Bolle (2):
  x86: use stdout if insn decoder test is successful
  x86: use stderr if insn sanity test fails

 arch/x86/tools/insn_sanity.c  | 3 ++-
 arch/x86/tools/test_get_len.c | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-10-25 20:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25 20:56 Paul Bolle [this message]
2016-10-25 20:56 ` [PATCH 1/2] x86: use stdout if insn decoder test is successful Paul Bolle
2016-10-26  6:54   ` [tip:x86/asm] x86/decoder: Use " tip-bot for Paul Bolle
2016-10-25 20:56 ` [PATCH 2/2] x86: use stderr if insn sanity test fails Paul Bolle
2016-10-26  6:55   ` [tip:x86/asm] x86/decoder: Use " tip-bot for Paul Bolle

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=1477428965-20548-1-git-send-email-pebolle@tiscali.nl \
    --to=pebolle@tiscali.nl \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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).