From: Johannes Berg <johannes@sipsolutions.net>
To: IgorMitsyanko <igor.mitsyanko.os@quantenna.com>
Cc: linux-wireless@vger.kernel.org, btherthala@quantenna.com,
hwang@quantenna.com, smaksimenko@quantenna.com,
dlebed@quantenna.com, Igor Mitsyanko <imitsyanko@quantenna.com>,
Kamlesh Rath <krath@quantenna.com>,
Sergey Matyukevich <smatyukevich@quantenna.com>,
Avinash Patil <avinashp@quantenna.com>,
Ben Hutchings <ben@decadent.org.uk>,
Kyle McMartin <kyle@kernel.org>
Subject: Re: [RFC] qtn: add FullMAC firmware for Quantenna QSR10G wifi device
Date: Mon, 14 Nov 2016 10:40:27 +0100 [thread overview]
Message-ID: <1479116427.9766.1.camel@sipsolutions.net> (raw)
In-Reply-To: <a5075f50-25c6-18a1-bd5b-309927dacdab@quantenna.com>
On Mon, 2016-11-14 at 11:26 +0300, IgorMitsyanko wrote:
> Thanks, Johannes.
>
> To clarify with you and Kalle, as persons involved with linux-
> wireless: is my understanding correct that submitting firmware into
> linux-fimware repository is a prerequisite to accepting new driver
> into linux-wireless?
I personally don't think it needs to be quite that strict, but I don't
think I've heard anyone else express an opinion either way.
Frankly, so far I only commented on the firmware patch because I
haven't had time to go over the driver code at all.
johannes
next prev parent reply other threads:[~2016-11-14 9:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1478700000-11624-1-git-send-email-igor.mitsyanko.os@quantenna.com>
2016-11-09 14:00 ` [PATCH V3] qtnfmac: announcement of new FullMAC driver for Quantenna chipsets igor.mitsyanko.os
2016-11-14 9:52 ` Johannes Berg
[not found] ` <62102ba6-cae0-f00d-f989-3f2e9ea43d9b@quantenna.com>
2016-11-16 16:50 ` IgorMitsyanko
2016-11-17 8:51 ` Johannes Berg
2016-11-15 9:06 ` Johannes Berg
2016-11-16 16:47 ` IgorMitsyanko
2016-11-17 7:54 ` Johannes Berg
2016-11-09 15:56 ` [RFC] qtn: add FullMAC firmware for Quantenna QSR10G wifi device Johannes Berg
[not found] ` <2fcb5f28-808e-f296-7e91-e5185e7577c9@quantenna.com>
2016-11-09 21:05 ` Johannes Berg
2016-11-10 14:02 ` IgorMitsyanko
2016-11-11 11:35 ` Johannes Berg
2016-11-14 8:26 ` IgorMitsyanko
2016-11-14 9:40 ` Johannes Berg [this message]
2016-11-23 15:25 ` Kalle Valo
2016-11-23 16:45 ` igor.mitsyanko.os
2016-11-23 17:09 ` IgorMitsyanko
2016-11-24 11:59 ` Kalle Valo
2016-11-25 10:16 ` IgorMitsyanko
2016-12-23 15:12 ` igor.mitsyanko.os
2016-12-23 17:47 ` Christian Lamparter
2016-11-22 14:44 ` IgorMitsyanko
2016-11-28 16:34 ` Kyle McMartin
2016-11-28 17:10 ` Oleksij Rempel
2016-11-28 17:33 ` Oleksij Rempel
2016-11-28 19:01 ` IgorMitsyanko
2016-11-29 3:49 ` Oleksij Rempel
2016-11-29 9:10 ` IgorMitsyanko
2016-11-29 9:34 ` Arend Van Spriel
2016-11-29 10:22 ` IgorMitsyanko
2016-11-28 22:07 ` IgorMitsyanko
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=1479116427.9766.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=avinashp@quantenna.com \
--cc=ben@decadent.org.uk \
--cc=btherthala@quantenna.com \
--cc=dlebed@quantenna.com \
--cc=hwang@quantenna.com \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=imitsyanko@quantenna.com \
--cc=krath@quantenna.com \
--cc=kyle@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=smaksimenko@quantenna.com \
--cc=smatyukevich@quantenna.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).