From: mcgrof@ruslug.rutgers.edu (Luis R. Rodriguez)
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
"Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com.br>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
prism54-devel@prism54.org
Subject: Re: Re: [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep
Date: Thu, 27 May 2004 15:45:13 -0400 [thread overview]
Message-ID: <20040527194513.GV3330@ruslug.rutgers.edu> (raw)
In-Reply-To: <40B6424D.7030203@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On Thu, May 27, 2004 at 03:32:29PM -0400, Jeff Garzik wrote:
> Marcelo Tosatti wrote:
> >IMO support for new hardware (new drivers) which dont break existing
> >setups are fine.
> >
> >Jeff, you are actively maintaining most of the network drivers in v2.4, if
> >you are OK with the inclusion of this, I'm OK.
> >
> >Does this make sense?
>
>
> Yup, makes sense and sounds good to me.
>
> Luis, feel free to send me the 2.4.x version of the prism54 driver --
> after addressing my comments, of course ;-)
Great. I'll fix all those patches up again for you and Marcelo. For future
development I've asked other prism54 developers to first send patches to
netdev for review/approval. Maybe we *should* do away with prism54-devel
mailing list and just use netdev as was once suggested by someone...
Luis
--
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84 A34A 6ADD 4937 E20A 525E
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-27 19:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 8:30 [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep Luis R. Rodriguez
2004-05-24 8:57 ` Luis R. Rodriguez
2004-05-27 18:10 ` Jeff Garzik
2004-05-27 19:27 ` Marcelo Tosatti
2004-05-27 19:32 ` Jeff Garzik
2004-05-27 19:45 ` Luis R. Rodriguez [this message]
2004-05-27 19:56 ` Jeff Garzik
2004-05-27 20:04 ` Luis R. Rodriguez
2004-05-27 18:19 ` Jeff Garzik
2004-05-27 18:25 ` Clint Adams
2004-05-27 18:40 ` Jeff Garzik
2004-05-27 19:05 ` [Prism54-devel] " Andrew Morton
2004-05-27 19:24 ` Jeff Garzik
2004-05-27 18:39 ` Jeff Garzik
[not found] <5.1.0.14.2.20040528090459.00ae3d18@pop.t-online.de>
2004-05-29 8:38 ` Luis R. Rodriguez
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=20040527194513.GV3330@ruslug.rutgers.edu \
--to=mcgrof@ruslug.rutgers.edu \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=marcelo.tosatti@cyclades.com.br \
--cc=mcgrof@studorgs.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.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).