From: Kenn Humborg <kenn@linux.ie>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: drivers/char/dz.[ch]: reason for keeping?
Date: Thu, 8 Apr 2004 22:23:50 +0100 [thread overview]
Message-ID: <20040408212350.GA30123@excalibur.research.wombat.ie> (raw)
In-Reply-To: <Pine.LNX.4.55.0404071304170.5705@jurand.ds.pg.gda.pl>
On Wed, Apr 07, 2004 at 01:16:48PM +0200, Maciej W. Rozycki wrote:
> On Sun, 4 Apr 2004, Jan-Benedict Glaw wrote:
> > Old ./drivers/char/dz.c + VAX changes + SERIO changes, that is :) I
> > guess best practice is that VAX people first merge up with MIPS folks,
> > then we snatch the old driver together and have a beer...
>
> It sounds like a plan. :-)
Sorry for coming in late on this.
There is no problem with dropping drivers/char/dz.[ch] from the official
tree. Us Linux/VAX guys work off our own CVS tree on SourceForge, so we
can continue to carry the drivers/char/dz.[ch] until we've got the
new driver working.
So, Jan-Benedict, there is no major panic to get the new driver working
for us before Rusty/Linus remove the old one.
Later,
Kenn (another Linux/VAX guy)
next prev parent reply other threads:[~2004-04-08 21:23 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 [this message]
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=20040408212350.GA30123@excalibur.research.wombat.ie \
--to=kenn@linux.ie \
--cc=jbglaw@lug-owl.de \
--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 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).