netdev
[Top] [All Lists]

Re: [Prism54-devel] Re: [PATCH 0/14] prism54: bring up to sync with pris

To: netdev@xxxxxxxxxxx, prism54-devel@xxxxxxxxxxx
Subject: Re: [Prism54-devel] Re: [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep
From: mcgrof@xxxxxxxxxxxxxxxxxxxx (Luis R. Rodriguez)
Date: Thu, 27 May 2004 16:04:14 -0400
In-reply-to: <40B647DB.4090109@xxxxxxxxx>
Mail-followup-to: netdev@xxxxxxxxxxx, prism54-devel@xxxxxxxxxxx
Organization: Rutgers University Student Linux Users Group
References: <20040524083003.GA3330@xxxxxxxxxxxxxxxxxx> <20040524085727.GR3330@xxxxxxxxxxxxxxxxxx> <40B62F29.6090101@xxxxxxxxx> <20040527192733.GB14186@xxxxxxxxxx> <40B6424D.7030203@xxxxxxxxx> <20040527194513.GV3330@xxxxxxxxxxxxxxxxxx> <40B647DB.4090109@xxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Thu, May 27, 2004 at 03:56:11PM -0400, Jeff Garzik wrote:
> 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.

Will do. My plan was for us to get the pathes for 2.6 all set. Once we
were all happy and our trees in sync we'd send a large 2.4 patch for
inclusion in 2.4

> Once the driver is merged, I do request split-up patches just like 2.6.x.

OK. Sure thing.

> >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 :)

I think we should. Anyone against this? Please reply or else we'll just
move to netdev.

        Luis

-- 
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E

Attachment: pgpKsGgy1wiMV.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>