linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Please pull 'upstream-jgarzik' branch of wireless-2.6
Date: Sat, 25 Aug 2007 02:40:39 -0400	[thread overview]
Message-ID: <46CFCEE7.4080009@garzik.org> (raw)
In-Reply-To: <20070815003637.GK7198@tuxdriver.com>

John W. Linville wrote:
> A few items intended for 2.6.24.
> 
> Individual patches here:
> 
> 	http://www.kernel.org/pub/linux/kernel/people/linville/wireless-2.6/upstream-jgarzik/
> 
> Thanks!
> 
> John
> 
> ---
> 
> The following changes since commit 39d3520c92cf7a28c07229ca00cc35a1e8026c77:
>   Linus Torvalds (1):
>         Linux 2.6.23-rc3
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git upstream-jgarzik
> 
> Daniel Drake (2):
>       zd1211rw: Add ID for Sitecom WL-162
>       zd1211rw: Add ID for ZyXEL M-202 XtremeMIMO
> 
> Mariusz Kozlowski (1):
>       drivers/net/wireless/wl3501_cs.c: remove redundant memset
> 
> Ulrich Kunitz (2):
>       zd1211rw: removed noisy debug messages
>       zd1211rw: consistent handling of ZD1211 specific rates
> 
>  drivers/net/wireless/wl3501_cs.c             |    1 -
>  drivers/net/wireless/zd1211rw/zd_chip.c      |   69 +++++++-----------
>  drivers/net/wireless/zd1211rw/zd_ieee80211.h |   43 +++++++----
>  drivers/net/wireless/zd1211rw/zd_mac.c       |   99 +++++++-------------------
>  drivers/net/wireless/zd1211rw/zd_mac.h       |   65 +++++++++++------
>  drivers/net/wireless/zd1211rw/zd_usb.c       |    2 +
>  6 files changed, 128 insertions(+), 151 deletions(-)

pulled



  reply	other threads:[~2007-08-25  6:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15  0:36 Please pull 'upstream-jgarzik' branch of wireless-2.6 John W. Linville
2007-08-25  6:40 ` Jeff Garzik [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-09-15 13:21 John W. Linville
2007-09-18  1:54 ` Zhu Yi
2007-08-28 23:17 John W. Linville
2007-08-31 13:44 ` 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=46CFCEE7.4080009@garzik.org \
    --to=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).