From: Jeff Garzik <jgarzik@pobox.com>
To: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
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: [Prism54-devel] Re: [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep
Date: Thu, 27 May 2004 15:56:11 -0400 [thread overview]
Message-ID: <40B647DB.4090109@pobox.com> (raw)
In-Reply-To: <20040527194513.GV3330@ruslug.rutgers.edu>
Luis R. Rodriguez wrote:
> 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
For what it's worth, you may send a "one big patch" to add the driver to
2.4, since the individual changes to that point will be in 2.6.x
BitKeeper changelog.
Once the driver is merged, I do request split-up patches just like 2.6.x.
> netdev for review/approval. Maybe we *should* do away with prism54-devel
> mailing list and just use netdev as was once suggested by someone...
Up to you :)
Jeff
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@pobox.com>
To: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
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:56:11 -0400 [thread overview]
Message-ID: <40B647DB.4090109@pobox.com> (raw)
In-Reply-To: <20040527194513.GV3330@ruslug.rutgers.edu>
Luis R. Rodriguez wrote:
> 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
For what it's worth, you may send a "one big patch" to add the driver to
2.4, since the individual changes to that point will be in 2.6.x
BitKeeper changelog.
Once the driver is merged, I do request split-up patches just like 2.6.x.
> netdev for review/approval. Maybe we *should* do away with prism54-devel
> mailing list and just use netdev as was once suggested by someone...
Up to you :)
Jeff
next prev parent reply other threads:[~2004-05-27 19:56 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
2004-05-27 19:45 ` [Prism54-devel] " Luis R. Rodriguez
2004-05-27 19:45 ` Luis R. Rodriguez
2004-05-27 19:56 ` Jeff Garzik [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 ` [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=40B647DB.4090109@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.