From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
"mcgrof@gmail.com" <mcgrof@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/4] wireless regulatory updates
Date: Fri, 24 Oct 2008 05:01:17 -0700 [thread overview]
Message-ID: <20081024120117.GH5951@tesla> (raw)
In-Reply-To: <20081024183219.735241000@sipsolutions.net>
On Fri, Oct 24, 2008 at 11:32:19AM -0700, Johannes Berg wrote:
> Here's my set of updates, it removes the struct hint entirely
> as we've come up with a new and better way.
These all look very sexy now, thanks.
Luis
next prev parent reply other threads:[~2008-10-24 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 18:32 [PATCH 0/4] wireless regulatory updates Johannes Berg
2008-10-24 12:01 ` Luis R. Rodriguez [this message]
2008-10-24 18:32 ` [PATCH 1/4] wireless: make regdom passing semantics simpler Johannes Berg
2008-10-24 18:32 ` [PATCH 2/4] wireless: remove struct regdom hinting Johannes Berg
2008-10-24 18:32 ` [PATCH 3/4] wireless: clean up regulatory ignore_request function Johannes Berg
2008-10-24 18:32 ` [PATCH 4/4] wireless regulatory: move ignore_request 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=20081024120117.GH5951@tesla \
--to=lrodriguez@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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).