From: Johannes Berg <johannes@sipsolutions.net>
To: "Chauhan, Rajesh" <rajeshc@qca.qualcomm.com>
Cc: "Rodriguez, Luis" <rodrigue@qca.qualcomm.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"Malinen, Jouni" <jouni@qca.qualcomm.com>,
"BAHINI, Henri" <hbahini@qca.qualcomm.com>,
"Johnson, Jeff" <jjohnson@qca.qualcomm.com>,
"Chang, Leo" <schang@qca.qualcomm.com>,
"Luo, Xun" <xunl@qca.qualcomm.com>,
"Thalappil, Sameer" <sameert@qca.qualcomm.com>,
"Hussain, Arif" <c_arifh@qca.qualcomm.com>
Subject: Re: [PATCHv3] cfg80211: add support for frequency interference event
Date: Sun, 17 Nov 2013 10:17:21 +0100 [thread overview]
Message-ID: <1384679841.14795.10.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <D19FD2B13A40CD4B8DA64DB9B8F112E936C4D635@nasanexd01a.na.qualcomm.com>
On Fri, 2013-11-15 at 18:53 +0000, Chauhan, Rajesh wrote:
> Hi Johannes,
>
> Could you pl. let us know of any further comments/feedback on patch set v3?
Trying to push me will make it likely that you get to drop to the bottom
of the pile. I have more than one thing to look at, as you may have
noticed.
johannes
next prev parent reply other threads:[~2013-11-17 9:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 19:32 [PATCHv3] cfg80211: add support for frequency interference event Rajesh Chauhan
2013-11-14 9:54 ` Luis R. Rodriguez
2013-11-15 18:53 ` Chauhan, Rajesh
2013-11-17 9:17 ` Johannes Berg [this message]
2013-12-03 13:25 ` Johannes Berg
2013-12-03 15:06 ` Johannes Berg
2013-12-03 16:35 ` Luis R. Rodriguez
2013-12-04 8:20 ` Johannes Berg
2013-12-04 8:20 ` Johannes Berg
2013-12-20 7:44 ` Chauhan, Rajesh
2013-12-20 8:11 ` Luis R. Rodriguez
2013-12-20 8:16 ` BAHINI, Henri
2013-12-20 8:26 ` Luis R. Rodriguez
2013-12-20 8:30 ` BAHINI, Henri
2013-12-20 8:37 ` Luis R. Rodriguez
2013-12-20 8:45 ` BAHINI, Henri
2014-01-06 16:38 ` 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=1384679841.14795.10.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=c_arifh@qca.qualcomm.com \
--cc=hbahini@qca.qualcomm.com \
--cc=jjohnson@qca.qualcomm.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rajeshc@qca.qualcomm.com \
--cc=rodrigue@qca.qualcomm.com \
--cc=sameert@qca.qualcomm.com \
--cc=schang@qca.qualcomm.com \
--cc=xunl@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).