From: Paul Albrecht <albrecht@rdi1.com>
To: linux-kernel@vger.kernel.org
Subject: What's up with 2.6.20?
Date: Fri, 08 Jun 2007 09:57:45 -0400 [thread overview]
Message-ID: <1181311065.3606.0.camel@albrecht.rdi1.com> (raw)
Hi,
I sent a message to the list yesterday describing a problem using via
hardware and a ps/2 keyboard for console input yesterday.
The reason I posted a description to the kernel mailing list is because
I have used the same software/hardware combination for some time and
only noticed the problem after upgrading the kernel from 2.6.13.2 to
2.6.20.
Seems like an obvious regression so I was wondering if I could get some
help resolving the problem here?
Paul Albrecht
next reply other threads:[~2007-06-08 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 13:57 Paul Albrecht [this message]
2007-06-08 15:06 ` Andrew Walrond
2007-06-08 14:38 ` Paul Albrecht
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=1181311065.3606.0.camel@albrecht.rdi1.com \
--to=albrecht@rdi1.com \
--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
all inboxes | Powered by JetHome®