From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, kathy.giori@atheros.com,
amod.bodas@atheros.com, david.quan@atheros.com,
michael.green@atheros.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 5/8] crda: synch up nl80211.h header with upstream for country flags
Date: Wed, 22 Dec 2010 15:02:31 +0100 [thread overview]
Message-ID: <1293026551.3531.22.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1292864555-28661-6-git-send-email-lrodriguez@atheros.com>
What's the point in two patches for this?
johannes
next prev parent reply other threads:[~2010-12-22 14:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 17:02 [PATCH 0/8] wireless: DFS region support Luis R. Rodriguez
2010-12-20 17:02 ` [PATCH 1/8] wireless-regdb: Add DFS bit fields for countries Luis R. Rodriguez
2010-12-22 13:58 ` Johannes Berg
2010-12-22 14:21 ` Luis R. Rodriguez
2010-12-20 17:02 ` [PATCH 1/2] cfg80211: process new country regulatory flags (DFS) Luis R. Rodriguez
2010-12-22 14:02 ` Johannes Berg
2010-12-22 14:29 ` Luis R. Rodriguez
2010-12-20 17:02 ` [PATCH 2/2] cfg80211: pass DFS region to drivers through reg_notifier() Luis R. Rodriguez
2010-12-21 10:53 ` Johannes Berg
2010-12-21 12:43 ` Luis R. Rodriguez
2010-12-22 14:03 ` Johannes Berg
2010-12-22 14:26 ` Luis R. Rodriguez
2010-12-20 17:02 ` [PATCH 4/8] crda: synch up nl80211.h copy file Luis R. Rodriguez
2010-12-20 17:02 ` [PATCH 5/8] crda: synch up nl80211.h header with upstream for country flags Luis R. Rodriguez
2010-12-22 14:02 ` Johannes Berg [this message]
2010-12-22 14:36 ` Luis R. Rodriguez
2010-12-20 17:02 ` [PATCH 1/2] iw: fix country print Luis R. Rodriguez
2010-12-20 17:02 ` [RFC 8/8] wireless-regdb: add FCC as the DFS region for US Luis R. Rodriguez
2011-01-04 18:49 ` [PATCH 0/8] wireless: DFS region support John W. Linville
2011-01-05 18:28 ` Luis R. Rodriguez
2011-01-05 18:30 ` John W. Linville
2011-01-05 21:26 ` 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=1293026551.3531.22.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=amod.bodas@atheros.com \
--cc=david.quan@atheros.com \
--cc=kathy.giori@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=michael.green@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).