From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: drivers/char/dz.[ch]: reason for keeping?
Date: Mon, 5 Apr 2004 14:19:57 +0100 [thread overview]
Message-ID: <20040405141957.B31724@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.55.0404051504080.31851@jurand.ds.pg.gda.pl>; from macro@ds2.pg.gda.pl on Mon, Apr 05, 2004 at 03:15:33PM +0200
On Mon, Apr 05, 2004 at 03:15:33PM +0200, Maciej W. Rozycki wrote:
> On Sun, 4 Apr 2004, Russell King wrote:
>
> > Since we have drivers/serial/dz.[ch] now merged, is there a reason to
> > keep drivers/char/dz.[ch] around any more? I notice people keep doing
> > cleanups, but this is wasted effort if the driver is superseded by the
> > new drivers/serial/dz.[ch] driver.
>
> drivers/char/dz.[ch] has been verified to work on real hardware, at least
> with 2.4. Can the same be said of drivers/serial/dz.[ch]? If so, then
> the former can be removed from the mainline.
Ralf has verified that it works before he submitted it to Linus, so
I guess that means that it does "work on real hardware".
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-04-05 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 9:12 drivers/char/dz.[ch]: reason for keeping? Russell King
2004-04-04 11:17 ` Jan-Benedict Glaw
2004-04-04 11:29 ` Russell King
2004-04-04 12:00 ` Jan-Benedict Glaw
2004-04-07 11:16 ` Maciej W. Rozycki
2004-04-07 12:39 ` Jan-Benedict Glaw
2004-04-07 13:27 ` Maciej W. Rozycki
2004-04-08 21:23 ` Kenn Humborg
2004-04-05 13:15 ` Maciej W. Rozycki
2004-04-05 13:19 ` Russell King [this message]
2004-04-05 13:35 ` Maciej W. Rozycki
2004-04-05 19:14 ` Ralf Baechle
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=20040405141957.B31724@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@linux-mips.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 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.