From: Lennert Buytenhek <buytenh@wantstofly.org>
To: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH 00/29] mwl8k update to version 0.10
Date: Wed, 19 Aug 2009 11:32:03 +0200 [thread overview]
Message-ID: <20090819093203.GA14050@mail.wantstofly.org> (raw)
In-Reply-To: <20090818103043.GA6171@mail.wantstofly.org>
On Tue, Aug 18, 2009 at 12:30:43PM +0200, Lennert Buytenhek wrote:
> The following changes since commit f0602f40fe362f4ee15aad719d5cf7021de61914:
> Bob Copeland (1):
> wl1251: correct definitions for 0th bit defines
>
> are available in the git repository at:
>
> git://git.marvell.com/mwl8k.git master
>
> Lennert Buytenhek (29):
> mwl8k: remove various unused struct members and defines
> mwl8k: s/IEEE80211_ADDR_LEN/ETH_ALEN/g
> mwl8k: sort firmware command list by opcode, and trim unused commands
> mwl8k: various coding style cleanups
> mwl8k: remove MWL8K_RADIO_* defines
> mwl8k: remove MWL8K_RADIO_*_PREAMBLE defines
> mwl8k: remove MWL8K_WMM_* defines
> mwl8k: remove MWL8K_*_SLOTTIME defines
> mwl8k: fix mwl8k_configure_filter() parameter lifetime issue
> mwl8k: ->add_interface() is not called for monitor interfaces
> mwl8k: dma header manipulations can't fail
> mwl8k: don't touch 'command done' interrupt during firmware load
> mwl8k: don't hardcode the number of transmit queues
> mwl8k: no need to hold ->tx_lock while setting the hardware interrupt mask
> mwl8k: implement rfkill
Johannes pointed out that this subject line is nonsense, which it
is as the patch itself implements IEEE80211_CONF_IDLE, so I've replaced
this commit message by "mwl8k: implement idle mode" and updated the
master branch (renaming the old one to master.old). No code changes.
prev parent reply other threads:[~2009-08-19 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 3:49 [PATCH 00/29] mwl8k update to version 0.10 Lennert Buytenhek
2009-08-18 10:30 ` Lennert Buytenhek
2009-08-19 9:32 ` Lennert Buytenhek [this message]
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=20090819093203.GA14050@mail.wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=johannes@sipsolutions.net \
--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 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).