From: Borislav Petkov <bp@suse.de>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-acpi@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
ying.huang@intel.com
Subject: Re: [PATCH] acpi/apei/erst: Remove "Error" from initialization and disable output
Date: Tue, 18 Jul 2017 16:07:29 +0200 [thread overview]
Message-ID: <20170718140729.GA20740@nazgul.tnic> (raw)
In-Reply-To: <0fb91e9d-5446-aa6e-2eea-c455538c4c1a@redhat.com>
On Tue, Jul 18, 2017 at 07:29:40AM -0400, Prarit Bhargava wrote:
> Boris, I'd agree with you but this is one of those places where I think we
> should bend a bit. Error and Warning are indications of a failure, and we
> should consider special casing them.
Woahahahahah, you're killing me! I haven't laughed so hard for a while
now. Thanks, I guess...
Special-casing "error" and "warning". Stop the presses, the kernel
decided to special-case two english words. News at 11.
> I would agree if this were one or two scripts but I've heard
> complaints from 3 different companies about this.
Three companies, huh? Three *whole* companies? Or just three engineers
who can't grep?
Of course, if you say three companies, that should at least give more
weight to your already insane argument.
Here's a counter-argument: with the gazillion abbreviations in dmesg,
actually having a print statement *explain* what it is trying to say is
refreshing and really helpful.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2017-07-18 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 0:21 [PATCH] acpi/apei/erst: Remove "Error" from initialization and disable output Prarit Bhargava
2017-07-18 5:26 ` Borislav Petkov
2017-07-18 11:29 ` Prarit Bhargava
2017-07-18 14:07 ` Borislav Petkov [this message]
2017-07-18 15:46 ` Linda Knippers
2017-07-18 16:38 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2017-05-02 13:14 Prarit Bhargava
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=20170718140729.GA20740@nazgul.tnic \
--to=bp@suse.de \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@intel.com \
--cc=ying.huang@intel.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