From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Laszlo Attila Toth <panther@balabit.hu>,
netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: keyboard dead with 45b5035
Date: Mon, 18 Feb 2008 20:50:01 +0100 [thread overview]
Message-ID: <200802182050.01964.rjw@sisk.pl> (raw)
In-Reply-To: <20080218185305.48a67587@mjolnir.drzeus.cx>
On Monday, 18 of February 2008, Pierre Ossman wrote:
> The patch "[RTNETLINK]: Send a single notification on device state changes." kills (at least)
> the keyboard here. Everything seems to work fine in single user mode, but when init starts
> spawning of logins, the keyboard goes bye-bye. Even the power button is ignored. :/
Please try with the patch from http://lkml.org/lkml/2008/2/18/331 .
Thanks,
Rafael
next prev parent reply other threads:[~2008-02-18 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 17:53 keyboard dead with 45b5035 Pierre Ossman
2008-02-18 19:50 ` Rafael J. Wysocki [this message]
2008-02-18 20:50 ` Pierre Ossman
2008-02-19 5:50 ` Pierre Ossman
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=200802182050.01964.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=panther@balabit.hu \
/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