From: Kalle Valo <kvalo@codeaurora•org>
To: Fuqian Huang <huangfq.daxian@gmail•com>
Cc: unlisted-recipients:; (no To-header on input) "David S . Miller"
<davem@davemloft•net>,
Arend van Spriel <arend.vanspriel@broadcom•com>,
Franky Lin <franky.lin@broadcom•com>,
Hante Meuleman <hante.meuleman@broadcom•com>,
Chi-Hsien Lin <chi-hsien.lin@cypress•com>,
Wright Feng <wright.feng@cypress•com>,
Igor Mitsyanko <imitsyanko@quantenna•com>,
Avinash Patil <avinashp@quantenna•com>,
Sergey Matyukevich <smatyukevich@quantenna•com>,
ath10k@lists•infradead.org, linux-wireless@vger•kernel.org,
netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
brcm80211-dev-list.pdl@broadcom•com,
brcm80211-dev-list@cypress•com,
Fuqian Huang <huangfq.daxian@gmail•com>
Subject: Re: [PATCH v3 20/24] wireless: Remove call to memset after dma_alloc_coherent
Date: Tue, 15 Oct 2019 05:21:22 +0000 (UTC) [thread overview]
Message-ID: <20191015052123.0040460A08@smtp.codeaurora.org> (raw)
In-Reply-To: <20190715031941.7120-1-huangfq.daxian@gmail.com>
Fuqian Huang <huangfq.daxian@gmail•com> wrote:
> In commit 518a2f1925c3
> ("dma-mapping: zero memory returned from dma_alloc_*"),
> dma_alloc_coherent has already zeroed the memory.
> So memset is not needed.
>
> Signed-off-by: Fuqian Huang <huangfq.daxian@gmail•com>
Patch applied to wireless-drivers-next.git, thanks.
52d4261862ec wireless: Remove call to memset after dma_alloc_coherent
--
https://patchwork.kernel.org/patch/11043359/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2019-10-15 5:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 3:19 [PATCH v3 20/24] wireless: Remove call to memset after dma_alloc_coherent Fuqian Huang
2019-07-15 9:06 ` Kalle Valo
2019-07-15 9:07 ` Kalle Valo
2019-10-15 5:21 ` 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=20191015052123.0040460A08@smtp.codeaurora.org \
--to=kvalo@codeaurora$(echo .)org \
--cc=huangfq.daxian@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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