From: Olaf Hering <olaf@aepfle.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <gregkh@suse.de>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [GIT PATCH] USB patches for 2.6.18
Date: Fri, 29 Sep 2006 08:24:30 +0200 [thread overview]
Message-ID: <20060929062430.GA28068@aepfle.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0609281815170.10847-100000@iolanthe.rowland.org>
On Thu, Sep 28, Alan Stern wrote:
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=115921335306280&w=2
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=115921335520143&w=2
This fixes the USB keyboard.
next prev parent reply other threads:[~2006-09-29 6:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 20:06 [GIT PATCH] USB patches for 2.6.18 Greg KH
2006-09-28 22:08 ` Olaf Hering
2006-09-28 22:18 ` [linux-usb-devel] " Alan Stern
2006-09-28 22:22 ` Linus Torvalds
2006-09-28 22:25 ` Greg KH
2006-09-28 22:41 ` Linus Torvalds
2006-09-28 22:47 ` Greg KH
2006-09-29 6:24 ` Olaf Hering [this message]
2006-09-29 11:19 ` Dmitry Torokhov
2006-10-07 17:59 ` Greg KH
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=20060929062430.GA28068@aepfle.de \
--to=olaf@aepfle.de \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@osdl.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