From: Ed Tomlinson <edt@aei.ca>
To: alpine.LNX.2.01.0910071706490.11297@dyndns.pervalidus.net
Cc: linux-kernel@vger.kernel.org, hirofumi@mail.parknet.co.jp,
alan@linux.intel.com
Subject: Re: keyboard under X with 2.6.31
Date: Sat, 10 Oct 2009 21:00:05 -0400 [thread overview]
Message-ID: <200910102100.06633.edt@aei.ca> (raw)
In-Reply-To: <4AD0EC21.6060204@yahoo.co.uk>
On Saturday 10 October 2009 16:18:41 Boyan wrote:
> e043e42bdb66885b3ac10d27a01ccb9972e2b0a3
You are not alone with keyboard problems in 31 in X. In my case I blamed a new wireless setup.
I am building with the the above commit reverted.
More to come,
Ed
next prev parent reply other threads:[~2009-10-11 1:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 20:18 keyboard under X with 2.6.31 Boyan
2009-10-11 1:00 ` Ed Tomlinson [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-11 6:34 Boyan
2009-10-11 20:39 ` Frédéric L. W. Meunier
2009-10-12 19:05 ` Marcin Slusarz
2009-10-15 18:31 ` Greg KH
2009-10-07 20:19 Frédéric L. W. Meunier
2009-10-09 2:38 ` Dmitry Torokhov
2009-10-09 2:55 ` Frédéric L. W. Meunier
2009-10-09 3:19 ` Justin P. Mattock
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=200910102100.06633.edt@aei.ca \
--to=edt@aei.ca \
--cc=alan@linux.intel.com \
--cc=alpine.LNX.2.01.0910071706490.11297@dyndns.pervalidus.net \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
/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