From: Steven Rostedt <rostedt@goodmis.org>
To: Keenan Pepper <keenanpepper@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, vojtech@suse.cz,
Andi Kleen <ak@suse.de>
Subject: Re: [PATCH] Disable the most annoying printk in the kernel
Date: Thu, 27 Oct 2005 10:39:09 -0400 [thread overview]
Message-ID: <1130423949.21118.112.camel@localhost.localdomain> (raw)
In-Reply-To: <4360DE89.6070802@gmail.com>
On Thu, 2005-10-27 at 10:04 -0400, Keenan Pepper wrote:
> Andi Kleen wrote:
> > Remove most useless printk in the world
>
> No way! I love that prink! =P
>
And you know, once it is gone, you will start getting reports from
people that their kernel doesn't act like it use to. Or they'll start
to think that their keyboards suddenly work better ;-)
-- Steve
> > Signed-off-by: Andi Kleen <ak@suse.de>
> >
> > Index: linux/drivers/input/keyboard/atkbd.c
> > ===================================================================
> > --- linux/drivers/input/keyboard/atkbd.c
> > +++ linux/drivers/input/keyboard/atkbd.c
> > @@ -328,7 +328,6 @@ static irqreturn_t atkbd_interrupt(struc
> > atkbd_report_key(&atkbd->dev, regs, KEY_HANJA, 3);
> > goto out;
> > case ATKBD_RET_ERR:
> > - printk(KERN_DEBUG "atkbd.c: Keyboard on %s reports too many keys pressed.
> > \n", serio->phys);
> > goto out;
> > }
> >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2005-10-27 14:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 8:26 [PATCH] Disable the most annoying printk in the kernel Andi Kleen
2005-10-27 14:04 ` Keenan Pepper
2005-10-27 14:39 ` Steven Rostedt [this message]
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
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=1130423949.21118.112.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=keenanpepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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