From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Andi Kleen <ak@suse.de>
Cc: Pavel Machek <pavel@suse.cz>, Lee Revell <rlrevell@joe-job.com>,
Hugh Dickins <hugh@veritas.com>,
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:40:01 +0100 [thread overview]
Message-ID: <20051028214000.GB24432@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200510282322.16627.ak@suse.de>
On Fri, Oct 28, 2005 at 11:22:15PM +0200, Andi Kleen wrote:
> On Friday 28 October 2005 22:59, Russell King wrote:
> > On Fri, Oct 28, 2005 at 10:51:32PM +0200, Pavel Machek wrote:
> > > 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.
> >
> > What do you suggest?
>
> Obviously it needs an DBUS over netlink interface with an user space daemon to open
> a window on the desktop. Then the user needs to click ok to make sure they
> understood they did something wrong (either by buying broken hardware or by simply
> typing).
>
> You get bonus points when that window first opens another window with a "Did you
> know ..." message with a little dancing pink penguin that gives you helpful tips
> regarding typing on keyboards and offers you links to buy new keyboards on the web.
>
> Wouldn't that be great?
Sounds like too much hastle. I heard an alternative suggestion somewhere
which I liked much better <evil grin>.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-10-28 21:40 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
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 [this message]
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=20051028214000.GB24432@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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
Powered by JetHome