From: Kalle Valo <kvalo@codeaurora.org>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: David Lin <dlin@marvell.com>,
Julian Calaby <julian.calaby@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
Chor Teck Law <ctlaw@marvell.com>,
"Pete Hsieh" <peteh@marvell.com>
Subject: Re: [PATCH v7] Add new mac80211 driver mwlwifi.
Date: Fri, 15 Apr 2016 15:40:45 +0300 [thread overview]
Message-ID: <87wpnzoxiq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <87lh4uc2xn.fsf@nemi.mork.no> ("Bjørn Mork"'s message of "Sun, 03 Apr 2016 14:05:56 +0200")
Bjørn Mork <bjorn@mork.no> writes:
> David Lin <dlin@marvell.com> writes:
>
>> We felt some resistance from various people, and get discouraged.
>
> Sorry to hear that. I believe this is a misunderstanding. I am
> convinced that *everyone* who commented on the driver did so with the
> intention to help getting it merged.
Exactly. Why would we otherwise spend so much time reviewing the driver
if we would not want it included?
> I for one would very much like to see this driver in mainline. But for
> that to happen, you wil have to:
> 1) create a feature frozen branch for mainline submission
> 2) respond relatively quickly to comments received, posting new
> versions of the patch set if necessary
>
> The main issue preventing this driver from being merged so far, in my
> view, is that you have continued to add features between each attemt to
> get it merged. Adding new features is of course not bad, but you should
> do that in another branch *until* the initial version is accepted.
Thanks for the good summary, I think we should even add that to our wiki
as a guideline for new drivers. Then submitting a new driver (or normal
patches for that matter) you really want to optimise the use of
reviewer's time. Just fix the issues pointed out in the review, don't do
anything extra as the chances are that it just slows down everything.
--
Kalle Valo
prev parent reply other threads:[~2016-04-15 12:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 3:51 [PATCH v7] Add new mac80211 driver mwlwifi David Lin
2015-11-12 19:47 ` Jes Sorensen
2015-11-26 8:34 ` David Lin
2015-11-20 11:22 ` Johannes Berg
2015-11-26 8:27 ` David Lin
2015-11-26 9:40 ` Johannes Berg
2015-11-27 2:00 ` David Lin
2015-11-27 8:27 ` Johannes Berg
2015-12-10 14:57 ` Kalle Valo
2015-12-15 7:54 ` David Lin
2015-12-10 14:06 ` Kalle Valo
[not found] ` <CANEJEGv7ENTJu4YHz1x2_ve2M6-3Nn8X-0aC2hA3o1mUs3tQ1g@mail.gmail.com>
2015-12-12 0:47 ` Grant Grundler
2015-12-14 11:47 ` Kalle Valo
2015-12-10 14:03 ` Kalle Valo
2015-12-10 14:39 ` Kalle Valo
2015-12-15 7:55 ` David Lin
2015-12-14 21:32 ` Kan Yan
2015-12-15 5:47 ` David Lin
2015-12-15 7:40 ` Emmanuel Grumbach
2015-12-15 7:53 ` David Lin
2016-03-16 23:24 ` Julian Calaby
2016-03-17 1:23 ` David Lin
2016-03-17 1:32 ` Julian Calaby
2016-03-17 2:10 ` David Lin
2016-04-03 12:05 ` Bjørn Mork
2016-04-15 12:40 ` Kalle Valo [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=87wpnzoxiq.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=bjorn@mork.no \
--cc=ctlaw@marvell.com \
--cc=dlin@marvell.com \
--cc=johannes@sipsolutions.net \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=peteh@marvell.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).