From: Zhu Yi <yi.zhu@intel.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: jeff@garzik.org, netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Please pull 'upstream-jgarzik' branch of wireless-2.6
Date: Tue, 18 Sep 2007 09:54:50 +0800 [thread overview]
Message-ID: <1190080490.5718.54.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20070915132134.GD6060@tuxdriver.com>
On Sat, 2007-09-15 at 09:21 -0400, John W. Linville wrote:
> Jeff,
>
> A few more for 2.6.24...
Hi John, how is the iwlwifi driver going? Would you like to push it to
Jeff for .24? Or you'd like me to create a patch against this branch?
Thanks,
-yi
next prev parent reply other threads:[~2007-09-18 2:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-15 13:21 Please pull 'upstream-jgarzik' branch of wireless-2.6 John W. Linville
2007-09-18 1:54 ` Zhu Yi [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-08 22:23 John W. Linville
2007-12-20 15:54 John W. Linville
2007-12-16 4:34 John W. Linville
2007-12-17 23:24 ` Jeff Garzik
2007-12-17 23:40 ` Jeff Garzik
2007-12-18 1:24 ` Zhu Yi
2007-12-04 13:59 John W. Linville
2007-12-04 20:13 ` Jeff Garzik
2007-11-27 14:47 John W. Linville
2007-11-27 16:08 ` Holger Schurig
2007-11-27 16:12 ` Dan Williams
2007-11-28 7:25 ` Holger Schurig
2007-11-27 18:55 ` John W. Linville
2007-12-04 13:55 ` John W. Linville
2007-11-06 1:16 John W. Linville
2007-11-06 17:43 ` Jeff Garzik
2007-08-28 23:17 John W. Linville
2007-08-31 13:44 ` Jeff Garzik
2007-08-15 0:36 John W. Linville
2007-08-25 6:40 ` Jeff Garzik
2007-08-06 20:14 Please pull 'fixes-jgarzik' " John W. Linville
2007-08-06 20:16 ` Please pull 'upstream-jgarzik' " John W. Linville
2007-08-07 22:21 ` Jeff Garzik
2007-07-18 2:19 John W. Linville
2007-07-18 22:31 ` Jeff Garzik
2007-07-10 18:57 John W. Linville
2007-07-16 21:59 ` 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=1190080490.5718.54.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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).