From: Greg KH <greg@kroah.com>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: Re : ANN: Linux 2.2 driver compatibility toolkit
Date: Wed, 12 Jun 2002 16:57:47 -0700 [thread overview]
Message-ID: <20020612235747.GD17306@kroah.com> (raw)
In-Reply-To: <20020610174050.A21783@bougret.hpl.hp.com> <3D07D022.5030106@mandrakesoft.com> <20020612162714.A24255@bougret.hpl.hp.com> <20020612233955.GC17306@kroah.com> <20020612165030.A24311@bougret.hpl.hp.com>
On Wed, Jun 12, 2002 at 04:50:30PM -0700, Jean Tourrilhes wrote:
> Don't rush, I'm not sure if you are done with USB
> changes. When the new HCD stuff will be in, I'm sure you will find
> something else to tinker with.
Heh, I _know_ I'm not done with USB changes :)
I'll just be backporting the ones that are now stable, and have been in
the tree for a long time. I'll not be backporting all of the new HCD
drivers for one.
Here's what I think I'll change in 2.4.20 that is now in the 2.5 tree:
- update the USB documentation
- remove the horrible typedefs in usb.h
- change usb_submit_urb and usb_alloc_urb apis
- add new drivers
- backport the usb-serial api and locking changes
And that will probably be enough for 2.4.20. In the meantime, the USB
changes in 2.5 will continue on, giving us more fodder to backport in
2.4.21, not to mention 2.2.22 :)
thanks,
greg k-h
next prev parent reply other threads:[~2002-06-13 0:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 0:40 Re : ANN: Linux 2.2 driver compatibility toolkit Jean Tourrilhes
2002-06-12 22:50 ` Jeff Garzik
2002-06-12 23:27 ` Jean Tourrilhes
2002-06-12 23:39 ` Greg KH
2002-06-12 23:50 ` Jean Tourrilhes
2002-06-12 23:57 ` Greg KH [this message]
2002-06-13 0:36 ` [linux-usb-devel] " Johannes Erdfelt
2002-06-13 4:31 ` 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=20020612235747.GD17306@kroah.com \
--to=greg@kroah.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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