From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] wireless: fix regdom passing semantics
Date: Wed, 22 Oct 2008 21:40:51 +0200 [thread overview]
Message-ID: <1224704451.30459.67.camel@johannes.berg> (raw)
In-Reply-To: <20081022123621.GJ6190@tesla>
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
On Wed, 2008-10-22 at 05:36 -0700, Luis R. Rodriguez wrote:
> On Wed, Oct 22, 2008 at 11:49:54AM -0700, Johannes Berg wrote:
> > The regdom struct is given to the core, so it might as well
> > free it in error conditions
>
> > the current documentation for
> > regulatory_hint doesn't note that you need to free it on errors
> > anyway.
>
> This last part is not accurate, typo again?
Ahrg. No, thinko. I only saw
- * @rd: a complete regulatory domain provided by the driver. If passed
- * the driver does not need to worry about freeing it.
not the fine print.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-10-22 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 9:02 [PATCH] wireless: fix regdom passing semantics Johannes Berg
2008-10-22 11:37 ` Luis R. Rodriguez
2008-10-22 18:47 ` Johannes Berg
2008-10-22 18:49 ` [PATCH v2] " Johannes Berg
2008-10-22 12:36 ` Luis R. Rodriguez
2008-10-22 19:40 ` Johannes Berg [this message]
2008-10-22 19:50 ` [PATCH v3] wireless: make regdom passing semantics simpler 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=1224704451.30459.67.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=Luis.Rodriguez@Atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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).