From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-wireless@vger.kernel.org
Subject: Re: Please pull patch-bomb for iwlwifi
Date: Wed, 25 Jul 2007 16:43:14 +0200
References: <20070725085754.GA670@mail.intel.com> <46A75CD9.9050100@garzik.org>
In-Reply-To: <46A75CD9.9050100@garzik.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Message-Id: <200707251643.14926.hs4233@mail.mn-solutions.de>
Sender: linux-wireless-owner@vger.kernel.org

> 1) You should post patches to the list for review.  Yes, even
> if there are 117 of them.  That is acceptable -- and
> encouraged -- mailing list etiquette.

Here I'm wondering if this is needed. For example, for the 
libertas WLAN driver we have an extra mailing list where people 
(mostly) post patches for review. Eventually, Dan Williams put 
them into his tree and then asks Linville to pull from him. But 
the patches in his GIT tree won't be sent to linux-wireless for 
individual review.

Now, isn't doing the iwlwifi project the same?  There is a 
mailinglist for this project 
(https://lists.sourceforge.net/lists/listinfo/ipw3945-devel) 
where anybody is free to join.

A cursory glance (I'm not in this mailing list) at 
http://sourceforge.net/mailarchive/forum.php?forum_name=ipw3945-devel 
shows that people indeed post patches there for review.

So, if you ask them to post each and every patch on 
linux-wireless, then other projects should do the same. Some 
projects (e.g. bcm43xx) mostly do cross-post. Is this the way 
people should go?