From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: [PATCH 0/2] the long-awaited bitrate/channel API update
Date: Thu, 24 Jan 2008 19:38:37 +0100 [thread overview]
Message-ID: <20080124183837.577631000@sipsolutions.net> (raw)
Having just rebased my patch on top of the new fixes Reinette posted
(thanks!) that were previously a show-stopper for iwlwifi, here's now
finally the submission of these two patches.
There will undoubtedly be bugs in this as I don't have the necessary
hardware to test, and I'm sure people will disagree with the regulatory
control change. I think we all agree, however, that the new API is
better and that the regulatory control configuration should be within
the new API. I will continue to work in this area but I hope that with
this patch in other people can help out as well, both fixing bugs and
fixing the small regulatory control regressions.
Since I know 1/2 won't make it to the list, here's the URL:
http://johannes.sipsolutions.net/patches/kernel/all/2008-01-24-18%3a41/018-cfg80211-channel-and-bitrate-api.patch
johannes
next reply other threads:[~2008-01-24 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 18:38 Johannes Berg [this message]
2008-01-24 18:38 ` [PATCH 1/2] cfg80211 API for channels/bitrates, mac80211 and driver conversion Johannes Berg
2008-01-28 0:49 ` Tomas Winkler
2008-01-28 15:10 ` John W. Linville
2008-01-28 16:23 ` Tomas Winkler
2008-01-28 18:23 ` John W. Linville
2008-01-29 14:05 ` Johannes Berg
2008-01-29 15:04 ` Tomas Winkler
2008-01-24 18:38 ` [PATCH 2/2] nl80211: export hardware bitrate/channel capabilities 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=20080124183837.577631000@sipsolutions.net \
--to=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 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.