linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
To: Russell King <rmk+lkml@arm.linux.org.uk>
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 15:35:35 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.55.0404051533450.31851@jurand.ds.pg.gda.pl> (raw)
In-Reply-To: <20040405141957.B31724@flint.arm.linux.org.uk>

On Mon, 5 Apr 2004, Russell King wrote:

> >  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".

 I see no problem then, though it's unfortunate I haven't got a note on
that.

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

  reply	other threads:[~2004-04-07  9:25 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
2004-04-05 13:35     ` Maciej W. Rozycki [this message]
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=Pine.LNX.4.55.0404051533450.31851@jurand.ds.pg.gda.pl \
    --to=macro@ds2.pg.gda.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).