From: Kalle Valo <kvalo@codeaurora.org>
To: Jonas Gorski <jogo@openwrt.org>
Cc: Avinash Patil <avinashp@quantenna.com>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
dlebed@quantenna.com, smaksimenko@quantenna.com,
smatyukevich@quantenna.com, imitsyanko@quantenna.com,
btherthala@quantenna.com, hwang@quantenna.com,
krath@quantenna.com
Subject: Re: [PATCH] qtnfmac: announcement of new FullMAC driver for Quantenna chipsets
Date: Sat, 04 Jun 2016 18:23:38 +0300 [thread overview]
Message-ID: <87wpm5rn9h.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAOiHx==C56Pj768bRX16VOaxj0Qf_oh5KXfhFJakT2zi-SokQQ@mail.gmail.com> (Jonas Gorski's message of "Sun, 29 May 2016 13:35:20 +0200")
Jonas Gorski <jogo@openwrt.org> writes:
> On 26 May 2016 at 20:52, Avinash Patil <avinashp@quantenna.com> wrote:
>
>> This email, including its contents and any attachment(s), may contain
>> confidential information of Quantenna Communications, Inc. and is
>> solely for the intended recipient(s). If you may have received this
>> in error, please contact the sender and permanently delete this
>> email, its contents and any attachment(s).
>
> You will need to remove this footer to be taken seriously, as
> confidential information would be not GPL compatible, and "may
> contain" means it is too risky to accept that.
Yeah, I'm not going to take (or even look) patches with such
disclaimers. So please resend so that we can start the review.
--
Kalle Valo
next prev parent reply other threads:[~2016-06-04 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 18:52 [PATCH] qtnfmac: announcement of new FullMAC driver for Quantenna chipsets Avinash Patil
2016-05-29 11:35 ` Jonas Gorski
2016-06-04 15:23 ` Kalle Valo [this message]
2016-06-08 11:22 ` Igor Mitsyanko
2016-06-08 11:35 ` Igor Mitsyanko
2016-06-08 13:25 ` Kalle Valo
2016-06-20 21:22 ` Igor Mitsyanko
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=87wpm5rn9h.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=avinashp@quantenna.com \
--cc=btherthala@quantenna.com \
--cc=dlebed@quantenna.com \
--cc=hwang@quantenna.com \
--cc=imitsyanko@quantenna.com \
--cc=jogo@openwrt.org \
--cc=johannes@sipsolutions.net \
--cc=krath@quantenna.com \
--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 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.