From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: "BAHINI, Henri" <hbahini@qca.qualcomm.com>
Cc: "Chauhan, Rajesh" <rajeshc@qca.qualcomm.com>,
Johannes Berg <johannes@sipsolutions.net>,
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: Fri, 20 Dec 2013 00:37:15 -0800 [thread overview]
Message-ID: <CAB=NE6WFOsjRgPyGjudc4c4JVoF-v=nnz2grknOai6=rYxrApA@mail.gmail.com> (raw)
In-Reply-To: <8AC12462F1AA0E4EA8FEB46307AAD6F650AAB122@nasanexd02f.na.qualcomm.com>
On Fri, Dec 20, 2013 at 12:30 AM, BAHINI, Henri
<hbahini@qca.qualcomm.com> 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.
Its not and this will depend on the driver / approach / and intent but
it does help.
> As for our effort for upstreaming our driver, we should take this out of this context since there
> are factors driving this that are completely orthogonal to this discussion.
That's true but it makes it harder for provide examples of the patches
you are introducing. Typically we just remove code that's unused. If
you have no intent on upstreaming then what's the point of doing tons
of review and consideration on API that we deeply care of for
userspace? The patch is debatable as-is already, I've provided my
feedback on it before and if you don't get good feedback from others
and also if some of this is because you are not upstreaming then I'm
trying to highlight for you that perhaps that should be of a little
more importance to you.
Luis
next prev parent reply other threads:[~2013-12-20 8:37 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 [this message]
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='CAB=NE6WFOsjRgPyGjudc4c4JVoF-v=nnz2grknOai6=rYxrApA@mail.gmail.com' \
--to=mcgrof@do-not-panic.com \
--cc=c_arifh@qca.qualcomm.com \
--cc=hbahini@qca.qualcomm.com \
--cc=jjohnson@qca.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--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 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).