From: "John W. Linville" <linville@tuxdriver.com>
To: davem@davemloft.net
Cc: jeff@garzik.org, netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Please pull 'fixes-davem' branch of wireless-2.6
Date: Wed, 7 Nov 2007 13:51:54 -0500 [thread overview]
Message-ID: <20071107185147.GA21097@tuxdriver.com> (raw)
In-Reply-To: <20071107001314.GH4440@tuxdriver.com>
Dave,
Hold-off on this one for now if -- clearly Johannes and I need to
brush-up on our Kconfig skills... :-(
I'll post a new pull request soon.
Thanks,
John
On Tue, Nov 06, 2007 at 07:13:14PM -0500, John W. Linville wrote:
> Dave,
>
> Here are some fixes for 2.6.24...
>
> The iwlwifi patch is needed because the iwlwifi drivers routinely end-up
> associated with the "simple" rate control algorithm, yet those drivers
> really only work with their own custom algorithms. The other rate
> control patches are there to satisfy dependencies for this patch.
>
> "mac80211: remove ieee80211_common.h" cleans-up an unused file left
> hanging-around after an earlier patch already in 2.6.24.
>
> "mac80211: remove unused driver ops" is really a clean-up, but
> "mac80211: use IW_AUTH_PRIVACY_INVOKED rather than IW_AUTH_KEY_MGMT"
> depends on it.
>
> "ssb: Fix initcall ordering" changes a subsys_initcall to an
> fs_initcall. This seems like a bit of a hack, but it fixes a real
> problem and I'm not sure what cleaner solution is either reasonable
> or available. The comment in the patch explains the reasoning for this
> somewhat unique situation.
>
> I think the other patches are plain enough to not require further
> comment. Let me know if there are any problems!
>
> Thanks,
>
> John
>
> ---
>
> Individual patches are available here:
>
> http://www.kernel.org/pub/linux/kernel/people/linville/wireless-2.6/fixes-davem/
>
> ---
>
> The following changes since commit 2655e2cee2d77459fcb7e10228259e4ee0328697:
> Alan Cox (1):
> ata_piix: Add additional PCI identifier for 40 wire short cable
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git fixes-davem
>
> Johannes Berg (9):
> softmac: fix wext MLME request reason code endianness
> mac80211: make simple rate control algorithm built-in
> mac80211: don't allow registering the same rate control twice
> mac80211: allow driver to ask for a rate control algorithm
> iwlwifi: select proper rate control algorithm
> softmac: MAINTAINERS update
> mac80211: remove ieee80211_common.h
> mac80211: remove unused driver ops
> mac80211: use IW_AUTH_PRIVACY_INVOKED rather than IW_AUTH_KEY_MGMT
>
> John W. Linville (1):
> mac80211: make "decrypt failed" messages conditional upon MAC80211_DEBUG
>
> Michael Buesch (5):
> ssb: Fix initcall ordering
> rfkill: Register LED triggers before registering switch
> rfkill: Use subsys_initcall
> rfkill: Use mutex_lock() at register and add sanity check
> rfkill: Fix sparse warning
>
> MAINTAINERS | 7 +--
> drivers/net/wireless/iwlwifi/iwl3945-base.c | 2 +
> drivers/net/wireless/iwlwifi/iwl4965-base.c | 2 +
> drivers/ssb/main.c | 5 +-
> include/net/mac80211.h | 26 ++------
> net/ieee80211/softmac/ieee80211softmac_wx.c | 2 +-
> net/mac80211/Kconfig | 12 ++++
> net/mac80211/Makefile | 3 +-
> net/mac80211/ieee80211.c | 16 +++++-
> net/mac80211/ieee80211_common.h | 91 ---------------------------
> net/mac80211/ieee80211_i.h | 2 +-
> net/mac80211/ieee80211_ioctl.c | 21 +++----
> net/mac80211/ieee80211_rate.c | 24 ++++++-
> net/mac80211/ieee80211_rate.h | 3 +
> net/mac80211/ieee80211_sta.c | 18 +++--
> net/mac80211/rc80211_simple.c | 25 +-------
> net/mac80211/rx.c | 2 +
> net/mac80211/wep.c | 2 +
> net/mac80211/wpa.c | 18 ++++--
> net/rfkill/rfkill.c | 37 ++++++-----
> 20 files changed, 126 insertions(+), 192 deletions(-)
> delete mode 100644 net/mac80211/ieee80211_common.h
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-11-07 18:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 0:13 Please pull 'fixes-davem' branch of wireless-2.6 John W. Linville
2007-11-07 14:38 ` Michael Buesch
2007-11-07 18:51 ` John W. Linville [this message]
2007-11-08 0:32 ` David Miller
2007-11-08 2:11 ` Please pull 'fixes-davem' branch of wireless-2.6 (this time for real!) John W. Linville
2007-11-11 6:02 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2008-01-16 21:26 Please pull 'fixes-davem' branch of wireless-2.6 John W. Linville
2008-01-18 12:33 ` David Miller
2008-01-08 5:14 John W. Linville
2008-01-08 5:21 ` David Miller
2007-12-20 15:52 John W. Linville
2007-12-20 17:39 ` Chatre, Reinette
2007-12-20 18:51 ` Chatre, Reinette
2007-12-20 19:55 ` John W. Linville
2007-12-25 6:07 ` David Miller
2007-12-17 20:54 John W. Linville
2007-12-18 6:56 ` David Miller
2007-11-30 3:31 John W. Linville
2007-11-30 12:34 ` Herbert Xu
2007-11-20 22:10 John W. Linville
2007-11-21 1:25 ` David Miller
2007-11-15 2:51 John W. Linville
2007-11-15 3:40 ` David Miller
2007-10-26 3:10 John W. Linville
2007-10-26 4:11 ` John W. Linville
2007-10-18 22:08 John W. Linville
2007-10-19 4:57 ` David Miller
2007-10-17 2:31 John W. Linville
2007-10-17 3:29 ` Michael Wu
2007-10-17 14:53 ` John W. Linville
2007-09-15 13:15 John W. Linville
2007-08-15 0:32 John W. Linville
2007-08-15 1:33 ` David Miller
2007-08-06 20:13 John W. Linville
2007-08-08 1:08 ` David Miller
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=20071107185147.GA21097@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--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).