linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Norik Dzhandzhapanyan <norikd@ethertronics.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] Per chain RSSI reporting
Date: Wed, 31 May 2017 12:52:37 +0000	[thread overview]
Message-ID: <87tw41mbnq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <SN1PR08MB1373BF583E9CE2AA6A0F6381B0FC0@SN1PR08MB1373.namprd08.prod.outlook.com> (Norik Dzhandzhapanyan's message of "Fri, 26 May 2017 22:49:45 +0000")

Norik Dzhandzhapanyan <norikd@ethertronics.com> writes:

> Add support for per chain RSSI reporting w/smoothing.
>
> Signed-off-by: Norik Dzhandzhapanyan norikd@ethertronics.com
>
>
> --- htt_rx.c.orig  2017-05-26 15:26:37.918504255 -0700
> +++ htt_rx.c        2017-05-26 12:10:33.139809025 -0700
> @@ -825,14 +825,71 @@ static bool ath10k_htt_rx_h_channel(stru
>               return true;
> }

The patch formatting is broken and I can't apply this. Please use git
send-email, more info here:

https://wireless.wiki.kernel.org/en/users/drivers/ath10k/submittingpatches

But more importantly:

> The contents of this transmission are Ethertronics Inc. Confidential
> and may contain proprietary or legally privileged information which
> may not be disclosed, copied or distributed without the express
> written consent of Ethertronics Inc. The information is intended to be
> for the use of the individual or entity named on this transmission. If
> you are not the intended recipient, be aware that any disclosure,
> copying, distribution or use of the contents of this information is
> prohibited. If you have received this transmission in error, please
> notify us by telephone immediately so that we can arrange for the
> retrieval of the original documents at no cost to you. Alternatively,
> notify the sender by replying to this transmission and delete the
> message without disclosing it. Thank you

I will never apply a patch which has this kind of disclaimer. The
patches must follow the Developer's Certificate of Origin[1] and not
have any other disclaimer.

[1] https://www.kernel.org/doc/html/latest/process/submitting-patches.html#=
sign-your-work-the-developer-s-certificate-of-origin

--=20
Kalle Valo=

      parent reply	other threads:[~2017-05-31 12:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 22:49 [PATCH] Per chain RSSI reporting Norik Dzhandzhapanyan
2017-05-27  1:12 ` Adrian Chadd
2017-05-27  2:09   ` Norik Dzhandzhapanyan
2017-05-27  8:30     ` Norik Dzhandzhapanyan
2017-05-27 16:07     ` Ben Greear
2017-05-27 16:39       ` Adrian Chadd
2017-05-27 17:56         ` Michael Ney
2017-05-27 19:30           ` Norik Dzhandzhapanyan
2017-05-27 22:10             ` Michael Ney
2017-05-28  1:22               ` Norik Dzhandzhapanyan
2017-05-27 19:31           ` Norik Dzhandzhapanyan
2017-05-27 19:25         ` Norik Dzhandzhapanyan
2017-05-27 21:38           ` Ben Greear
     [not found]             ` <SN1PR08MB13736CC61B1D00ED2968CF5CB0FD0@SN1PR08MB1373.namprd08.prod.outlook.com>
2017-05-27 21:49               ` Ben Greear
2017-05-30 13:23                 ` Matthias May
2017-05-31 13:05     ` Kalle Valo
2017-05-31 12:53   ` Kalle Valo
2017-05-31 12:52 ` 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=87tw41mbnq.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=norikd@ethertronics.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).