netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "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: [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep
Date: Thu, 27 May 2004 16:27:34 -0300	[thread overview]
Message-ID: <20040527192733.GB14186@logos.cnet> (raw)
In-Reply-To: <40B62F29.6090101@pobox.com>

On Thu, May 27, 2004 at 02:10:49PM -0400, Jeff Garzik wrote:
> Luis R. Rodriguez wrote:
> >BTW we can supply a 2.4 prism54 patch (as new driver). Would that be
> >wanted?
> 
> No objections here.
> 
> 2.4.x is vaguely closed, though, so Marcelo may not be interested in new 
> drivers.

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?

  reply	other threads:[~2004-05-27 19:27 UTC|newest]

Thread overview: 14+ 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 [this message]
2004-05-27 19:32       ` Jeff Garzik
2004-05-27 19:45         ` Luis R. Rodriguez
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

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=20040527192733.GB14186@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).