mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Hugh Dickins <hugh@veritas.com>, Andi Kleen <ak@suse.de>,
	vojtech@suse.cz, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Disable the most annoying printk in the kernel
Date: Fri, 28 Oct 2005 22:51:32 +0200	[thread overview]
Message-ID: <20051028205132.GB11397@elf.ucw.cz> (raw)
In-Reply-To: <1130532239.4363.125.camel@mindpipe>

Hi!

> > > > Remove most useless printk in the world
> > > 
> > > It warns about crappy keyboards. It triggers regulary for me on x32,
> > > (probably because of my weird capslock+x+s etc combination). It is
> > > usefull as a warning "this keyboard is crap" and "no, bad mechanical switch
> > > is not the reason for lost key".
> > 
> > Okay, if you want a message to remind you that your keyboard is crap
> > several times a day, please keep your own patch to do so.  Let the
> > rest of the world go with Andi's patch.
> 
> Plus keyboards are a dime a dozen these days, they give you one with
> every server whether or not you want it.  If you have rack full of 1U
> servers the pile of keyboards will be as high as the rack.  I wish our
> KVM vendor would come haul them away.

Well, keyboard detected and reported an error. Kernel reacted with
printk(). You are removing that printk(). I can understand that,
printk is really annoying, but I really believe _some_ error handling
should be added there if you remove the printk.
								Pavel
-- 
Thanks, Sharp!

  reply	other threads:[~2005-10-28 20:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27  8:26 Andi Kleen
2005-10-27 14:04 ` Keenan Pepper
2005-10-27 14:39   ` Steven Rostedt
2005-10-27 22:00     ` Jan Engelhardt
2005-10-27 18:03 ` Ingo Oeser
2005-10-27 23:23   ` jerome lacoste
2005-10-28  7:20 ` Pavel Machek
2005-10-28 18:43   ` Andi Kleen
2005-10-28 18:52     ` Andre Eisenbach
2005-10-28 18:50   ` Hugh Dickins
2005-10-28 20:43     ` Lee Revell
2005-10-28 20:51       ` Pavel Machek [this message]
2005-10-28 20:59         ` Russell King
2005-10-28 21:20           ` Jan Engelhardt
2005-10-28 21:22           ` Andi Kleen
2005-10-28 21:40             ` Russell King
2005-10-28 22:41             ` Jon Masters
2005-10-28 21:23           ` Pavel Machek
2005-10-28 21:36             ` Russell King
2005-10-29 15:40             ` Ingo Oeser
2005-10-29  7:45           ` Pavel Machek
2005-10-29 15:36       ` Ingo Oeser
     [not found] <52bjf-680-9@gated-at.bofh.it>
     [not found] ` <52Hj9-3e6-27@gated-at.bofh.it>
     [not found]   ` <52HCr-3CO-7@gated-at.bofh.it>
     [not found]     ` <52JkU-6gS-29@gated-at.bofh.it>
     [not found]       ` <52JuY-6s7-21@gated-at.bofh.it>
2005-10-28 22:18         ` Bodo Eggert

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=20051028205132.GB11397@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --cc=vojtech@suse.cz \
    /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®