From: Johannes Berg <johannes@sipsolutions.net>
To: "Nagarajan, Ashok Raj" <arnagara@qti.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Manoharan, Rajkumar" <rmanohar@qti.qualcomm.com>,
"Thiagarajan, Vasanthakumar" <vthiagar@qti.qualcomm.com>
Subject: Re: [PATCH] cfg80211: add debugfs VHT80 allow map
Date: Mon, 09 Feb 2015 11:16:51 +0100 [thread overview]
Message-ID: <1423477011.2110.8.camel@sipsolutions.net> (raw)
In-Reply-To: <1423466162219.33842@qti.qualcomm.com>
[please don't top-post]
On Mon, 2015-02-09 at 07:16 +0000, Nagarajan, Ashok Raj wrote:
> Hi Johannes,
>
> I see your point here. I will upload one patch for printing this info from iw.
>
> I will also write another patch for removing HT40 one?
Sounds fine - any complaints from others?
johannes
prev parent reply other threads:[~2015-02-09 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 6:35 [PATCH] cfg80211: add debugfs VHT80 allow map Ashok Raj Nagarajan
2015-02-06 19:11 ` Johannes Berg
2015-02-09 7:16 ` Nagarajan, Ashok Raj
2015-02-09 10:16 ` 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=1423477011.2110.8.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arnagara@qti.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rmanohar@qti.qualcomm.com \
--cc=vthiagar@qti.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).