From: Nuri Jawad <lkml@jawad.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Re: Remove silly messages from input layer.
Date: Mon, 8 May 2006 20:21:16 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0605081950210.4170@pc> (raw)
Joseph Fannin wrote:
>Spamming my logs with these messages so often that my dmesg buffer
>soon contains nothing but and I have to use grep -v to read my syslog
>is not user-friendly, and I am hardly a novice.
I don't doubt that, but we're going in circles here. I never alleged this
message was useful for everyone, but it IS useful for users with a working
keyboard and specifically with mechanical switches (can be triggered by a
loose cable or too slow turning of the dial, this a few times repeated can
cause the keyboard *port* to lock up, requiring a reboot).
If you have broken hardware that keeps triggering an error message that
is valid and informative for a majority of users, use the source and
comment it out. Nobody has a problem with that.
But don't try something that will leave us with no error messages left in
the long run because somebody somewhere with broken hard- or software got
spammed by them.
To the topic starter: calling such a message "silly" is pretty silly. And
that from a distro maintainer..
Regards, Nuri
reply other threads:[~2006-05-08 18:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.64.0605081950210.4170@pc \
--to=lkml@jawad.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®