From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC v3] cfg80211 API for channels/bitrates, mac80211 and driver conversion
Date: Thu, 10 Jan 2008 18:31:27 +0100 [thread overview]
Message-ID: <1199986287.3861.91.camel@johannes.berg> (raw)
In-Reply-To: <1199967423.3861.51.camel@johannes.berg> (sfid-20080110_121725_060148_B022943A)
[-- Attachment #1: Type: text/plain, Size: 426 bytes --]
On Thu, 2008-01-10 at 13:17 +0100, Johannes Berg wrote:
> This patch creates new cfg80211 wiphy API for channel and bitrate
> registration and converts mac80211 and drivers to the new API. The
> old mac80211 API is completely ripped out. All drivers (except ath5k)
> are updated to the new API, in many cases I expect that optimisations
> can be done.
Tested with iwl4965 and found two bugs, will repost.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-01-11 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 12:17 [RFC v3] cfg80211 API for channels/bitrates, mac80211 and driver conversion Johannes Berg
2008-01-10 17:31 ` Johannes Berg [this message]
2008-01-11 11:59 ` Johannes Berg
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=1199986287.3861.91.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@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