From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wireless: remove struct regdom hinting
Date: Wed, 22 Oct 2008 04:39:50 -0700 [thread overview]
Message-ID: <20081022113950.GE6190@tesla> (raw)
In-Reply-To: <1224585042.5521.7.camel@johannes.berg>
On Tue, Oct 21, 2008 at 03:30:42AM -0700, Johannes Berg wrote:
> --- everything.orig/net/wireless/reg.h 2008-10-21 11:16:54.000000000 +0200
> +++ everything/net/wireless/reg.h 2008-10-21 11:43:18.000000000 +0200
> @@ -11,30 +11,21 @@ int set_regdom(const struct ieee80211_re
>
> /**
> * __regulatory_hint - hint to the wireless core a regulatory domain
> - * @wiphy: if a driver is providing the hint this is the driver's very
> - * own &struct wiphy
> + * @wiphy: if the hint comes from country information from an AP, this
> + * is required to be set to the wiphy that received the information
> * @alpha2: the ISO/IEC 3166 alpha2 being claimed the regulatory domain
> - * should be in. If @rd is set this should be NULL
> - * @rd: a complete regulatory domain, if passed the caller need not worry
> - * about freeing it
> + * should be in. If @rd is set this should be NULL
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That can be removed from kdoc as @rd is gone now. Also can you
please update Documentation/networking/regulatory.txt to reflect the
new changes for mortals?
Luis
next prev parent reply other threads:[~2008-10-22 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 10:30 [PATCH] wireless: remove struct regdom hinting Johannes Berg
2008-10-22 11:39 ` Luis R. Rodriguez [this message]
2008-10-22 18:51 ` [PATCH v2] " Johannes Berg
2008-10-22 12:29 ` Luis R. Rodriguez
2008-10-22 19:31 ` Johannes Berg
2008-10-22 12:41 ` Luis R. Rodriguez
2008-10-22 19:43 ` Johannes Berg
2008-10-22 14:36 ` Luis R. Rodriguez
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=20081022113950.GE6190@tesla \
--to=lrodriguez@atheros.com \
--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).