mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nuri Jawad <lkml@jawad.org>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Remove silly messages from input layer.
Date: Thu, 4 May 2006 16:59:28 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0605041644260.32501@pc> (raw)
In-Reply-To: <20060504024404.GA17818@redhat.com>

On Wed, 3 May 2006, Dave Jones wrote:

> The latter message seems to trigger with certain keyboard switchers
> and again, does nothing but confuse people.

I rather think it's showing us there was a glitch when switching.

I have a mechanical switch that sometimes produces this message, and every 
now and then, the keyboard loses its key repeat time/rate setting.
It often happens when the switch is not turned quickly or firmly enough 
and in such a case I had the keyboard port lock up completely a few times. 
I think the kernel should report such a situation.

If people are "confused" by valid error messages, they can use certain 
proprietary operating systems that hide the ugly truth from them. What's 
next, removing "access beyond end of device"? I want to stay informed if 
my mechanical switch produces glitches. There are electronic ones that 
don't.

It would be nice if kernel messages had a structure that allowed a 
verbosity setting, but until then, non-confused users want the 
information they can get.

Regards, Nuri

  parent reply	other threads:[~2006-05-04 14:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04  2:44 Dave Jones
2006-05-04  7:13 ` Pavel Machek
2006-05-04  7:17 ` Pavel Machek
2006-05-04 15:08   ` Martin J. Bligh
2006-05-04 18:34     ` Dmitry Torokhov
2006-05-04 18:38       ` Dave Jones
2006-05-05 10:31         ` Pavel Machek
2006-05-05 10:39           ` Sergei Organov
2006-05-05 10:51             ` Valdis.Kletnieks
2006-05-05 15:27           ` Dave Jones
2006-05-05 15:37             ` Martin Mares
2006-05-05 15:46               ` Dave Jones
2006-05-05 15:54                 ` Martin Mares
2006-05-05 16:00                   ` Dave Jones
2006-05-05 16:12                     ` Martin Mares
2006-05-05 19:59                     ` Nuri Jawad
2006-05-05 20:06                       ` Martin Bligh
2006-05-05 20:30                         ` Nuri Jawad
2006-05-07  8:07                           ` Joseph Fannin
2006-05-08  6:43             ` Helge Hafting
2006-05-08  7:25               ` Con Kolivas
2006-05-09  6:54                 ` Helge Hafting
2006-05-04 19:14       ` Hugh Dickins
2006-05-04 15:45   ` David Greaves
2006-05-06 18:51     ` Jindrich Makovicka
2006-05-04 14:59 ` Nuri Jawad [this message]
2006-05-04 19:24   ` Hua Zhong

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.0605041644260.32501@pc \
    --to=lkml@jawad.org \
    --cc=davej@redhat.com \
    --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®