From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, henrique.gobbi@cyclades.com,
support@stallion.oz.au, R.E.Wolff@BitWizard.nl, paulus@samba.org,
elfert@de.ibm.com, felfert@millenux.com, gerg@snapgear.com,
kuba@mareimbrium.org
Subject: Re: [2/3]
Date: Thu, 15 Jan 2004 16:54:34 -0800 [thread overview]
Message-ID: <20040116005434.GH23253@kroah.com> (raw)
In-Reply-To: <20040113173352.D7256@flint.arm.linux.org.uk>
On Tue, Jan 13, 2004 at 05:33:52PM +0000, Russell King wrote:
> ===== drivers/usb/serial/ftdi_sio.c 1.55 vs edited =====
> --- 1.55/drivers/usb/serial/ftdi_sio.c Tue Oct 28 13:44:01 2003
> +++ edited/drivers/usb/serial/ftdi_sio.c Tue Jan 13 14:16:51 2004
Yeah, this ended up here due to a bad merge a few kernel releases ago.
I have the fix for this driver in my queue of USB patches to send off to
Linus soon.
Sorry about this.
Nice job in fixing up all of the other drivers, that was a big effort.
greg k-h
next prev parent reply other threads:[~2004-01-16 1:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 11:00 [PROBLEM] ircomm ioctls Jozef Vesely
2004-01-13 11:36 ` Russell King
2004-01-13 11:49 ` Outstanding fixups (was: Re: [PROBLEM] ircomm ioctls) Russell King
2004-01-13 17:15 ` Russell King
2004-01-13 17:24 ` [1/3] Serial fixups (mostly tested) Russell King
2004-01-24 6:16 ` [lkml] pseudo tty / kernel compile question Karl Tatgenhorst
2004-01-25 21:53 ` David Woodhouse
2004-01-13 17:33 ` [2/3] Russell King
2004-01-13 17:55 ` [2/3] Henrique Oliveira
2004-01-13 18:53 ` [2/3] John Stoffel
2004-01-13 22:15 ` [2/3] Paul Mackerras
2004-01-14 7:01 ` [2/3] Benjamin Herrenschmidt
2004-01-16 11:34 ` [2/3] Matthias Urlichs
2004-01-16 0:54 ` Greg KH [this message]
2004-01-18 12:43 ` [2/3] Greg Ungerer
2004-01-18 15:42 ` [2/3] Russell King
2004-01-18 23:23 ` [2/3] Greg Ungerer
2004-01-13 17:42 ` [3/3] 2.6 broken serial drivers Russell King
2004-01-13 20:21 ` Andrew Morton
2004-01-13 21:10 ` Russell King
2004-01-18 16:16 ` Russell King
2004-01-14 12:42 ` Maciej W. Rozycki
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=20040116005434.GH23253@kroah.com \
--to=greg@kroah.com \
--cc=R.E.Wolff@BitWizard.nl \
--cc=elfert@de.ibm.com \
--cc=felfert@millenux.com \
--cc=gerg@snapgear.com \
--cc=henrique.gobbi@cyclades.com \
--cc=kuba@mareimbrium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=support@stallion.oz.au \
/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