All of lore.kernel.org
 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: Mon, 16 Jul 2007 17:59:20 -0400	[thread overview]
Message-ID: <469BEA38.2040804@garzik.org> (raw)
In-Reply-To: <20070710185758.GH7927@tuxdriver.com>

John W. Linville wrote:
> The following changes since commit 71780f59e127bb281a9302d430495ca9586c14e7:
>   Linus Torvalds (1):
>         Merge branch 'for-linus' of git://git.kernel.org/.../ieee1394/linux1394-2.6
> 
> are found in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git upstream-jgarzik
> 
> Adrian Bunk (1):
>       drivers/net/wireless/libertas/wext.c: remove dead code
> 
> Dan Williams (1):
>       libertas: fix disabling WPA
> 
> Daniel Drake (4):
>       zd1211rw: Allow channels 1-11 for unrecognised regulatory domains
>       zd1211rw: Detect more AL2230S radios
>       zd1211rw: Add ID for Buffalo WLI-U2-KG54L
>       zd1211rw: Defer firmware load until first ifup
> 
> Holger Schurig (1):
>       libertas: fix use-after-free in rx path
> 
> Jean Tourrilhes (1):
>       softmac: Fix ESSID problem
> 
> Matthias Kaehlcke (1):
>       use list_for_each_entry() for iteration in Prism 54 driver
> 
> Michael Wu (1):
>       rtl8187: fix endianness issue in rtl8225 register writing
> 
> Michal Schmidt (5):
>       airo: disable the PCI device when unloading module
>       airo: delay some initialization until the netdev is up
>       airo: fix a race causing initialization failures
>       airo: simpler calling convention for enable_MAC()
>       airo: start with radio off
> 
> Robert P. J. Day (1):
>       WIRELESS: Remove clearly obsolete libertas/version.h file.
> 
> Stephen Hemminger (2):
>       ipw2200: rf kill switch polling power saving
>       ipw2100: RF kill switch timer power save

pulled



  reply	other threads:[~2007-07-16 21:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 18:57 Please pull 'upstream-jgarzik' branch of wireless-2.6 John W. Linville
2007-07-16 21:59 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-07-18  2:19 John W. Linville
2007-07-18 22:31 ` 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-08-15  0:36 John W. Linville
2007-08-25  6:40 ` Jeff Garzik
2007-08-28 23:17 John W. Linville
2007-08-31 13:44 ` Jeff Garzik
2007-09-15 13:21 John W. Linville
2007-09-18  1:54 ` Zhu Yi
2007-11-06  1:16 John W. Linville
2007-11-06 17:43 ` 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-12-04 13:59 John W. Linville
2007-12-04 20:13 ` Jeff Garzik
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-20 15:54 John W. Linville
2008-01-08 22:23 John W. Linville

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=469BEA38.2040804@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.