From: Jeff Garzik <jeff@garzik.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Please pull 'upstream' branch of wireless-2.6 (2007-02-14)
Date: Sat, 17 Feb 2007 15:24:27 -0500 [thread overview]
Message-ID: <45D7647B.8090704@garzik.org> (raw)
In-Reply-To: <20070214212817.GB28318@tuxdriver.com>
John W. Linville wrote:
> Some late-breaking small and/or important changes before the 2.6.21
> merge window closes...
>
> ---
>
> The following changes since commit 46b8c85e1df091fe2d53ae7d02addb0dc58a9123:
> Larry Finger (1):
> ieee80211: Fix sparse warning
>
> are found in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git upstream
>
> Ahmed S. Darwish (4):
> ipw2100: Use ARRAY_SIZE macro when appropriate
> misc-wireless: Use ARRAY_SIZE macro when appropriate
> hostap: Use ARRAY_SIZE macro when appropriate
> wavelan: Use ARRAY_SIZE macro when appropriate
>
> Dan Williams (1):
> prism54: correct assignment of DOT1XENABLE in WE-19 codepaths
>
> Daniel Drake (1):
> zd1211rw: Readd zd_addr_t cast
>
> Ingo van Lil (1):
> wireless: fix IW_IS_{GET,SET} comment in wireless.h
>
> Larry Finger (5):
> bcm43xx: Janitorial change - remove two unused variables
> bcm43xx: Fix for oops on resume
> bcm43xx: Fix for 4311 and 02/07/07 specification changes
> bcm43xx: OFDM fix for rev 1 cards
> ieee80211softmac: Fix setting of initial transmit rates
>
> Michael Buesch (1):
> bcm43xx: Ignore ampdu status reports
ACK. Tried to pull, but there were conflicts with netdev#upstream.
Since there are dependencies in netdev#upstream, looks like you need to
resend against that.
next prev parent reply other threads:[~2007-02-17 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 21:28 Please pull 'upstream' branch of wireless-2.6 (2007-02-14) John W. Linville
2007-02-17 20:24 ` Jeff Garzik [this message]
2007-02-17 23:36 ` John W. Linville
2007-02-20 16:28 ` 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=45D7647B.8090704@garzik.org \
--to=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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.