From: David Miller <davem@davemloft.net>
To: huangfq.daxian@gmail.com
Cc: jes@trained-monkey.org, linux-hippi@sunsite.dk,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 18/24] hippi: Remove call to memset after pci_alloc_consistent
Date: Mon, 15 Jul 2019 11:06:51 -0700 (PDT) [thread overview]
Message-ID: <20190715.110651.1919532320008372502.davem@davemloft.net> (raw)
In-Reply-To: <20190715031921.7028-1-huangfq.daxian@gmail.com>
From: Fuqian Huang <huangfq.daxian@gmail.com>
Date: Mon, 15 Jul 2019 11:19:21 +0800
> pci_alloc_consistent calls dma_alloc_coherent directly.
> 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>
Applied.
prev parent reply other threads:[~2019-07-15 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 3:19 [PATCH v3 18/24] hippi: Remove call to memset after pci_alloc_consistent Fuqian Huang
2019-07-15 18:06 ` David Miller [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=20190715.110651.1919532320008372502.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=huangfq.daxian@gmail.com \
--cc=jes@trained-monkey.org \
--cc=linux-hippi@sunsite.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).