linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Please pull patch-bomb for iwlwifi
Date: Wed, 25 Jul 2007 16:35:11 +0100	[thread overview]
Message-ID: <20070725153511.GA11785@infradead.org> (raw)
In-Reply-To: <200707251643.14926.hs4233@mail.mn-solutions.de>

On Wed, Jul 25, 2007 at 04:43:14PM +0200, Holger Schurig wrote:
> > 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.

And libertas is the shiny example for a properly written wireless driver,
riiiight?


  parent reply	other threads:[~2007-07-25 15:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25  8:57 Please pull patch-bomb for iwlwifi Zhu Yi
2007-07-25  9:48 ` Andy Green
2007-07-25 14:23 ` Jeff Garzik
2007-07-25 14:43   ` Holger Schurig
2007-07-25 15:12     ` Andy Green
2007-07-25 15:15     ` Jeff Garzik
2007-07-25 15:35     ` Christoph Hellwig [this message]
2007-07-25 20:40     ` Dan Williams
2007-07-25 19:01   ` John W. Linville
2007-07-25 21:20     ` Jeff Garzik
2007-07-25 20:07 ` John W. Linville
2007-07-25 21:00   ` Tomas Winkler
2007-07-25 21:26     ` Jeff Garzik
2007-07-25 21:53       ` Tomas Winkler
2007-07-26  1:55   ` Zhu Yi
  -- strict thread matches above, loose matches on Subject: below --
2007-06-08 22:15 James Ketrenos

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=20070725153511.GA11785@infradead.org \
    --to=hch@infradead.org \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=linux-wireless@vger.kernel.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).