From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Luca Tettamanti" <kronos.it@gmail.com>
Cc: "Vojtech Pavlik" <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] atkbd: disable spurious ACK/NAK warning on panic
Date: Mon, 13 Nov 2006 16:24:41 -0500 [thread overview]
Message-ID: <d120d5000611131324q3c124ae9h969adc18e35ee350@mail.gmail.com> (raw)
In-Reply-To: <20061113204340.GA25557@dreamland.darkstar.lan>
On 11/13/06, Luca Tettamanti <kronos.it@gmail.com> wrote:
> After the panic() message has been printed kernel may blink keyboard
> leds to signal the abnormal condition.
> atkbd warns that "Some program might be trying access hardware directly"
> at every blink, scrolling the useful text out of the screen.
> Avoid printing the warning when oops_in_progress is set in order to
> preserve the panic message.
>
Hi Luca,
Current input git tree already has code in i8042 supressing extra ACKs
caused by palic blinks; as soon as Linus pulls from me you should not
see these messages anymore.
--
Dmitry
next prev parent reply other threads:[~2006-11-13 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 20:43 Luca Tettamanti
2006-11-13 21:24 ` Dmitry Torokhov [this message]
2006-11-13 21:39 ` Luca Tettamanti
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=d120d5000611131324q3c124ae9h969adc18e35ee350@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=kronos.it@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
all inboxes | Powered by JetHome®