All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Rajesh Chauhan <rajeshc@qca.qualcomm.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Jouni Malinen <jouni@qca.qualcomm.com>,
	"Bahini, Henri" <hbahini@qca.qualcomm.com>,
	Jeff Johnson <jjohnson@qca.qualcomm.com>,
	"Chang, Leo" <schang@qca.qualcomm.com>,
	"Luo, Xun" <xunl@qca.qualcomm.com>,
	sameert@qca.qualcomm.com, c_arifh@qca.qualcomm.com
Subject: Re: [PATCHv3] cfg80211: add support for frequency interference event
Date: Wed, 04 Dec 2013 09:20:41 +0100	[thread overview]
Message-ID: <1386145241.4284.5.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1386145204.4284.4.camel@jlt4.sipsolutions.net> (sfid-20131204_092013_820427_3AA619B7)

On Wed, 2013-12-04 at 09:20 +0100, Johannes Berg wrote:
> On Tue, 2013-12-03 at 17:35 +0100, Luis R. Rodriguez wrote:
> > On Tue, Dec 3, 2013 at 2:25 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
> > >> + * @interference_source: enum nl80211_freq_interference_source_type
> > >> + *   is used to specify source of interference.
> > >
> > > Do we expect that different sources would be treated differently? If
> > > not, what use is this?
> > 
> > That was because of my nagging, without such a field the type of
> > interference would be completely ambiguous and we'd have no users on
> > the Linux kernel of this API,
> 
> Wait, we have no users for this API? Forget it then - I thought you were
> going to post a patch soon. I guess I should have learned by now not to
> trust QCA with this.
> 
> I'll drop this until I see a patch using it.

You can see this as a carrot (or stick, depending on how you look at it)
for upstreaming the driver that wants it.

johannes


  reply	other threads:[~2013-12-04  8:20 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
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 [this message]
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=1386145241.4284.5.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=mcgrof@do-not-panic.com \
    --cc=rajeshc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.