From: Johannes Berg <johannes@sipsolutions.net>
To: "BAHINI, Henri" <hbahini@qca.qualcomm.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
"Chauhan, Rajesh" <rajeshc@qca.qualcomm.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"Malinen, Jouni" <jouni@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: Mon, 06 Jan 2014 17:38:10 +0100 [thread overview]
Message-ID: <1389026290.5891.34.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <8AC12462F1AA0E4EA8FEB46307AAD6F650AAB122@nasanexd02f.na.qualcomm.com>
On Fri, 2013-12-20 at 08:30 +0000, BAHINI, Henri wrote:
> Please do educate us a bit!
> We were not aware of the requirement that all patches contributions to
> the cfg/nl have to be for driver that are already up streamed.
You're adding code that needs to be maintained, thought about when
changing other things, etc. I don't see why we as the community should
shoulder that burden if you're not even willing to upstream the code
using it. It feels like you're just dumping code that you happen to need
today over the wall.
We've never really had to even consider this situation because you're
the first to actively work on cfg80211/nl80211 while apparently not even
thinking about upstreaming your driver!
johannes
prev parent reply other threads:[~2014-01-06 16:38 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
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 [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=1389026290.5891.34.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.