From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Linux Kernel List <linux-kernel@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: drivers/char/dz.[ch]: reason for keeping?
Date: Sun, 4 Apr 2004 12:29:58 +0100 [thread overview]
Message-ID: <20040404122958.A14991@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040404111712.GE27362@lug-owl.de>; from jbglaw@lug-owl.de on Sun, Apr 04, 2004 at 01:17:12PM +0200
On Sun, Apr 04, 2004 at 01:17:12PM +0200, Jan-Benedict Glaw wrote:
> The VAX port also (still) uses a modified version of the d/c/dz.[ch]
> driver. Also, the MIPS guys may have some outstanding patches...
It is my understanding that the MIPS people are happy with the new
dz.c, since I passed it to them to test and submit. Since they
submitted it, I think we can assume that they're happy.
So we just need the VAX people to confirm that the new driver works
for them, and then for _someone_ to remove the old driver (either
the MIPS or the VAX people.)
> While at it, I've already implemented some SERIO changes. That'll allow
> the dz.c driver to announce that it waits for LK-style keyboard on one
> port and VSXXX-style mouse/digitizer on the 2nd port...
Which dz.c ? 8)
--
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-04 11:30 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 [this message]
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
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=20040404122958.A14991@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--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.