From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: "silexcommon@gmail.com" <silexcommon@gmail.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
Alagu Sankar <alagusankar@silex-india.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 01/11] ath10k_sdio: sdio htt data transfer fixes
Date: Wed, 4 Oct 2017 08:55:47 +0000 [thread overview]
Message-ID: <878tgrxpf1.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <59D1EC94.2020307@broadcom.com> (Arend van Spriel's message of "Mon, 2 Oct 2017 09:36:52 +0200")
Arend van Spriel <arend.vanspriel@broadcom.com> writes:
> On 9/30/2017 7:37 PM, silexcommon@gmail.com wrote:
>> From: Alagu Sankar <alagusankar@silex-india.com>
>>
>
> [...]
>
>>
>> Signed-off-by: Alagu Sankar <alagusankar@silex-india.com>
>
> Not really have a specific remark for this patch, but for the entire
> series. These patches are sent using an anonymous email address, apart
> from 'silex' being in there, which does not show up in the certificate
> of origin. Just wondering if this is acceptable?
As long as there's the "correct" From header as the first line in the
commit log, which git then uses as the author instead of the From line
from email header. And I see Alagu doing that here so there shouldn't be
any problems.
--=20
Kalle Valo=
next prev parent reply other threads:[~2017-10-04 8:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 17:37 [PATCH 00/11] SDIO support for ath10k silexcommon
2017-09-30 17:37 ` [PATCH 01/11] ath10k_sdio: sdio htt data transfer fixes silexcommon
2017-10-02 7:36 ` Arend van Spriel
2017-10-02 7:44 ` Alagu Sankar
2017-10-04 8:55 ` Kalle Valo [this message]
2017-09-30 17:37 ` [PATCH 02/11] ath10k_sdio: wb396 reference card fix silexcommon
2017-10-01 22:47 ` Steve deRosier
2017-10-02 7:02 ` Alagu Sankar
2017-10-02 9:06 ` Erik Stromdahl
2017-09-30 17:37 ` [PATCH 03/11] ath10k_sdio: DMA bounce buffers for read write silexcommon
2017-12-22 16:08 ` Kalle Valo
2017-12-25 12:26 ` Alagu Sankar
2017-12-25 16:11 ` Adrian Chadd
2017-12-27 18:49 ` Arend van Spriel
2017-12-27 19:26 ` Adrian Chadd
2018-01-08 12:58 ` Kalle Valo
2017-09-30 17:37 ` [PATCH 04/11] ath10k_sdio: reduce transmit msdu count silexcommon
2017-09-30 17:37 ` [PATCH 05/11] ath10k_sdio: use clean packet headers silexcommon
2017-09-30 17:37 ` [PATCH 06/11] ath10k_sdio: high latency fixes for beacon buffer silexcommon
2017-09-30 17:37 ` [PATCH 07/11] ath10k_sdio: fix rssi indication silexcommon
2017-09-30 17:37 ` [PATCH 08/11] ath10k_sdio: common read write silexcommon
2017-10-04 9:49 ` Kalle Valo
2017-10-05 10:09 ` [08/11] " Gary Bisson
2017-10-05 17:33 ` Alagu Sankar
2017-12-08 14:42 ` Gary Bisson
2017-09-30 17:37 ` [PATCH 09/11] ath10k_sdio: virtual scatter gather for receive silexcommon
2017-10-04 19:56 ` Erik Stromdahl
2017-09-30 17:37 ` [PATCH 10/11] ath10k_sdio: enable firmware crash dump silexcommon
2017-09-30 17:37 ` [PATCH 11/11] ath10k_sdio: hif start once addition silexcommon
2017-10-02 9:02 ` [PATCH 00/11] SDIO support for ath10k Erik Stromdahl
2017-10-04 6:22 ` Alagu Sankar
2017-10-04 15:53 ` Erik Stromdahl
2017-10-05 15:12 ` Gary Bisson
2017-10-05 17:24 ` Alagu Sankar
2017-10-06 11:16 ` Gary Bisson
2017-12-18 16:19 ` Gary Bisson
2017-12-22 16:21 ` Kalle Valo
2017-12-22 16:25 ` Kalle Valo
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=878tgrxpf1.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=alagusankar@silex-india.com \
--cc=arend.vanspriel@broadcom.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=silexcommon@gmail.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).