From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755552AbcJYU4U (ORCPT ); Tue, 25 Oct 2016 16:56:20 -0400 Received: from lb2-smtp-cloud3.xs4all.net ([194.109.24.26]:46182 "EHLO lb2-smtp-cloud3.xs4all.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753930AbcJYU4S (ORCPT ); Tue, 25 Oct 2016 16:56:18 -0400 From: Paul Bolle To: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" Cc: Andrew Morton , 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 Message-Id: <1477428965-20548-1-git-send-email-pebolle@tiscali.nl> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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