From: Jeff Garzik <jeff@garzik.org>
To: yi.zhu@intel.com
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: Please pull patch-bomb for iwlwifi
Date: Wed, 25 Jul 2007 10:23:21 -0400 [thread overview]
Message-ID: <46A75CD9.9050100@garzik.org> (raw)
In-Reply-To: <20070725085754.GA670@mail.intel.com>
Zhu Yi wrote:
> Hi,
>
> This patch series catches wireless-dev up to the stand-alone
> iwlwifi tree version 0.1.3.
>
> There are totally 117 patches so I won't post them one by one on
> the list. Please find the commit series for the changes in the
> patch bomb:
>
> iwlwifi-efe55d8fa702a23724bf44fdd54059f8c4480941.tgz
> at
> http://intellinuxwireless.org/iwlwifi/patches/
Based on a brief glance, patches look good to me. Thanks!
Two suggestions:
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.
2) I would recommend submitting via git. Auke @ Intel does this with
e100/e1000/etc. stuff and it works great.
The main suggestion is #1, since it is important to post patches to
linux-wireless. #2 is more in the realm of linville's preference.
Jeff
next prev parent reply other threads:[~2007-07-25 14:23 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 [this message]
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
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=46A75CD9.9050100@garzik.org \
--to=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=yi.zhu@intel.com \
/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).