From: Jeff Garzik <jeff@garzik.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Please pull 'upstream' branch of wireless-2.6
Date: Wed, 09 May 2007 18:54:59 -0400 [thread overview]
Message-ID: <46425143.9040403@garzik.org> (raw)
In-Reply-To: <20070508173907.GH6479@tuxdriver.com>
John W. Linville wrote:
> The following changes since commit 5b94f675f57e4ff16c8fda09088d7480a84dcd91:
> Linus Torvalds (1):
> Merge master.kernel.org:/.../davem/sparc-2.6
>
> are found in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git upstream
>
> Daniel Drake (1):
> zd1211rw: Add ID for ZyXEL AG-225H v2
>
> Larry Finger (3):
> ieee80211: add ieee80211_channel_to_freq
> ieee80211: include frequency in scan results
> bcm43xx: Remove dead configuration variable CONFIG_947XX
>
> Matthew Davidson (1):
> zd1211rw: Add ID for Sitecom WL-117
>
> Ulrich Kunitz (1):
> zd1211rw: Added new USB id for Planex GW-US54ZGL
>
> drivers/net/wireless/bcm43xx/bcm43xx.h | 18 +-----
> drivers/net/wireless/bcm43xx/bcm43xx_dma.c | 4 -
> drivers/net/wireless/bcm43xx/bcm43xx_main.c | 81 ---------------------------
> drivers/net/wireless/bcm43xx/bcm43xx_main.h | 19 ------
> drivers/net/wireless/zd1211rw/zd_usb.c | 4 +
> include/net/ieee80211.h | 2 +
> net/ieee80211/ieee80211_geo.c | 16 +++++
> net/ieee80211/ieee80211_wx.c | 8 ++-
> 8 files changed, 31 insertions(+), 121 deletions(-)
pulled
next prev parent reply other threads:[~2007-05-09 22:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 17:39 Please pull 'upstream' branch of wireless-2.6 John W. Linville
2007-05-08 17:41 ` Please pull 'upstream-rtl8187' " John W. Linville
2007-05-09 23:12 ` Jeff Garzik
2007-05-10 2:16 ` Michael Wu
2007-05-10 4:21 ` Jeff Garzik
2007-05-10 4:47 ` Michael Wu
2007-05-10 11:23 ` Michael Buesch
2007-05-10 11:36 ` David Miller
2007-05-09 22:54 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-29 18:30 Please pull 'upstream-fixes' " John W. Linville
2007-05-29 18:31 ` Please pull 'upstream' " John W. Linville
2007-05-30 14:03 ` Jeff Garzik
2007-05-07 17:51 John W. Linville
2007-05-07 21:15 ` Dan Williams
2007-05-07 22:51 ` John W. Linville
2007-05-08 8:49 ` Johannes Berg
2007-05-07 23:09 ` Jeff Garzik
2007-05-07 23:30 ` Michael Wu
2007-05-07 23:38 ` John W. Linville
2007-05-08 17:38 ` John W. Linville
2007-03-27 18:26 Please pull 'upstream-fixes' " John W. Linville
2007-03-27 18:26 ` Please pull 'upstream' " John W. Linville
2007-03-29 12:31 ` Jeff Garzik
2007-03-16 21:31 Please pull 'upstream-fixes' " John W. Linville
2007-03-16 21:34 ` Please pull 'upstream' " John W. Linville
2007-03-23 5:55 ` Jeff Garzik
2007-03-23 12:02 ` Dan Williams
2007-03-08 3:30 Please pull 'upstream-fixes' " John W. Linville
2007-03-08 3:32 ` Please pull 'upstream' " John W. Linville
2007-03-09 16:59 ` Jeff Garzik
2007-02-27 20:50 Please pull 'upstream-fixes' " John W. Linville
2007-02-27 20:51 ` Please pull 'upstream' " John W. Linville
2007-03-03 0:42 ` Jeff Garzik
2007-02-02 21:27 Please pull "upstream-fixes" " John W. Linville
2007-02-02 21:28 ` Please pull "upstream" " John W. Linville
2007-02-07 0:06 ` Please pull "upstream-fixes" " Jeff Garzik
2007-02-07 21:11 ` Please pull "upstream" " John W. Linville
2007-02-09 20:13 ` John W. Linville
2007-02-09 21:12 ` 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=46425143.9040403@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).