From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: "Theodore Y. Ts'o" <tytso@MIT.EDU>,
rgooch@ras.ucalgary.ca, jgarzik@mandrakesoft.mandrakesoft.com,
dhinds@valinux.com, linux-kernel@vger.kernel.org
Subject: Re: Serial cardbus code.... for testing, please.....
Date: Sun, 10 Dec 2000 11:24:13 -0500 [thread overview]
Message-ID: <3A33AE2D.A8E6053@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10012100814230.2635-100000@penguin.transmeta.com>
Linus Torvalds wrote:
> Oh, serial_cb shouldn't work anyway, I think.
As soon as the serial.c hotplug patch appear, you'll be receiving a
patch that eliminates serial_cb.
Jeff
--
Jeff Garzik |
Building 1024 | These are not the J's you're lookin' for.
MandrakeSoft | It's an old Jedi mind trick.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-10 16:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.1001003164737.31485F-100000@mandrakesoft.mandrakesoft.com>
[not found] ` <200010032248.SAA23371@tsx-prime.MIT.EDU>
[not found] ` <200010040118.e941IuF00625@vindaloo.ras.ucalgary.ca>
2000-12-08 18:05 ` Serial cardbus code.... for testing, please tytso
2000-12-08 21:27 ` Linus Torvalds
2000-12-08 21:34 ` David Hinds
2000-12-09 5:41 ` Theodore Y. Ts'o
2000-12-09 7:41 ` Linus Torvalds
2000-12-09 16:13 ` Jeff Garzik
2000-12-10 8:22 ` Theodore Y. Ts'o
2000-12-10 16:26 ` Jeff Garzik
2000-12-10 7:07 ` Theodore Y. Ts'o
2000-12-10 16:19 ` Linus Torvalds
2000-12-10 16:24 ` Jeff Garzik [this message]
2000-12-10 16:33 ` Jeff Garzik
2000-12-10 18:32 ` Alan Cox
2000-12-09 7:48 ` Linus Torvalds
2000-12-09 13:54 ` Jens Taprogge
2000-12-09 18:13 ` Linus Torvalds
2000-12-10 7:55 ` Theodore Y. Ts'o
2000-12-11 2:57 ` Chris Wedgwood
2000-12-11 21:14 ` David Hinds
2000-12-13 16:18 ` tytso
2000-12-14 21:25 ` tytso
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=3A33AE2D.A8E6053@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=dhinds@valinux.com \
--cc=jgarzik@mandrakesoft.mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
--cc=torvalds@transmeta.com \
--cc=tytso@MIT.EDU \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.