From: Jeff Garzik <jgarzik@pobox.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
"Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>
Cc: 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: [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep
Date: Thu, 27 May 2004 15:32:29 -0400 [thread overview]
Message-ID: <40B6424D.7030203@pobox.com> (raw)
In-Reply-To: <20040527192733.GB14186@logos.cnet>
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 ;-)
Jeff
next prev parent reply other threads:[~2004-05-27 19:33 UTC|newest]
Thread overview: 20+ 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-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 [this message]
2004-05-27 19:45 ` [Prism54-devel] " Luis R. Rodriguez
2004-05-27 19:45 ` Luis R. Rodriguez
2004-05-27 19:56 ` [Prism54-devel] " Jeff Garzik
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 ` [Prism54-devel] " Clint Adams
2004-05-27 18:25 ` Clint Adams
2004-05-27 18:40 ` [Prism54-devel] " Jeff Garzik
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 19:24 ` Jeff Garzik
2004-05-27 18:39 ` Jeff Garzik
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=40B6424D.7030203@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--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 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.