From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Fuqian Huang <huangfq.daxian@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jaroslav Kysela <perex@perex.cz>,
Richard Fontana <rfontana@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev@lists.ozlabs.org,
Allison Randal <allison@lohutok.net>
Subject: Re: [PATCH v2 27/27] sound: ppc: remove unneeded memset after dma_alloc_coherent
Date: Fri, 28 Jun 2019 10:59:51 +0200 [thread overview]
Message-ID: <83108dee-72f7-e56f-95f6-26162c9a0ccc@c-s.fr> (raw)
In-Reply-To: <20190628025055.16242-1-huangfq.daxian@gmail.com>
Le 28/06/2019 à 04:50, Fuqian Huang a écrit :
> In commit af7ddd8a627c
> ("Merge tag 'dma-mapping-4.21' of git://git.infradead.org/users/hch/dma-mapping"),
> dma_alloc_coherent has already zeroed the memory.
> So memset is not needed.
You are refering to a merge commit, is that correct ?
I can't see anything related in that commit, can you please pinpoint it ?
As far as I can see, on powerpc the memory has always been zeroized
(since 2005 at least).
Christophe
>
> Signed-off-by: Fuqian Huang <huangfq.daxian@gmail.com>
> ---
> sound/ppc/pmac.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/sound/ppc/pmac.c b/sound/ppc/pmac.c
> index 1b11e53f6a62..1ab12f4f8631 100644
> --- a/sound/ppc/pmac.c
> +++ b/sound/ppc/pmac.c
> @@ -56,7 +56,6 @@ static int snd_pmac_dbdma_alloc(struct snd_pmac *chip, struct pmac_dbdma *rec, i
> if (rec->space == NULL)
> return -ENOMEM;
> rec->size = size;
> - memset(rec->space, 0, rsize);
> rec->cmds = (void __iomem *)DBDMA_ALIGN(rec->space);
> rec->addr = rec->dma_base + (unsigned long)((char *)rec->cmds - (char *)rec->space);
>
>
next prev parent reply other threads:[~2019-06-28 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 2:50 Fuqian Huang
2019-06-28 8:59 ` Christophe Leroy [this message]
2019-06-28 9:11 ` Fuqian Huang
2019-06-28 9:17 ` [alsa-devel] " Takashi Iwai
2019-06-28 9:48 ` Christophe Leroy
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=83108dee-72f7-e56f-95f6-26162c9a0ccc@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=allison@lohutok.net \
--cc=alsa-devel@alsa-project.org \
--cc=gregkh@linuxfoundation.org \
--cc=huangfq.daxian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=perex@perex.cz \
--cc=rfontana@redhat.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®