From: Ben Collins <bcollins@debian.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCHES] USB input layer improvements
Date: Mon, 5 May 2003 23:18:30 -0400 [thread overview]
Message-ID: <20030506031830.GC679@phunnypharm.org> (raw)
In-Reply-To: <20030506002233.GY679@phunnypharm.org>
On Mon, May 05, 2003 at 08:22:33PM -0400, Ben Collins wrote:
> Ok, now I'm sending this here since linux-usb-devel and Pavel seem to be
> ignoring my emails. Note, this is against 2.4.21-rc1, but I am prepared
> to finish this off for 2.5 aswell. I just need someone who knows USB to
> look this over and give me some freaking feedback. The multi-input patch
> seems to be of significant importance.
My mistake on the name drop. I sent the patch to Vojtech Pavlik.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
next prev parent reply other threads:[~2003-05-06 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 0:22 [PATCHES] USB input layer improvements Ben Collins
2003-05-06 3:18 ` Ben Collins [this message]
2003-05-06 23:45 ` Greg KH
2003-05-07 1:34 ` Ben Collins
2003-05-07 7:18 ` Vojtech Pavlik
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=20030506031830.GC679@phunnypharm.org \
--to=bcollins@debian.org \
--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