From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: linux-wireless@vger.kernel.org, smihir@qti.qualcomm.com,
tushnimb@qca.qualcomm.com
Subject: Re: [PATCH 1/2] cfg80211: enable regulatory hints for strict custom settings
Date: Fri, 11 Oct 2013 15:32:07 +0200 [thread overview]
Message-ID: <1381498327.14293.16.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1380763990-5981-1-git-send-email-mcgrof@do-not-panic.com> (sfid-20131003_033318_437971_39C28D59)
APplied both, but there were issues (fuzz) - please check.
Also, fixed your typo in the subject :)
johannes
prev parent reply other threads:[~2013-10-11 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 1:33 [PATCH 1/2] cfg80211: enable regulatory hints for strict custom settings Luis R. Rodriguez
2013-10-03 1:33 ` [PATCH 2/2] cfg80211: simplfy strict custom alpha2 regdomain check Luis R. Rodriguez
2013-10-11 13:32 ` Johannes Berg [this message]
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=1381498327.14293.16.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=smihir@qti.qualcomm.com \
--cc=tushnimb@qca.qualcomm.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).