From: Takashi Iwai <tiwai@suse.de>
To: Christophe Leroy <christophe.leroy@c-s.fr>
Cc: Rob Herring <robh@kernel.org>,
alsa-devel@alsa-project.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
Paul Mackerras <paulus@samba.org>,
Fuqian Huang <huangfq.daxian@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 41/87] sound: ppc: remove memset after dma_alloc_coherent
Date: Fri, 28 Jun 2019 11:12:38 +0200 [thread overview]
Message-ID: <s5himsq6pkp.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5hmui26qet.wl-tiwai@suse.de>
On Fri, 28 Jun 2019 10:54:34 +0200,
Takashi Iwai wrote:
>
> On Fri, 28 Jun 2019 10:53:14 +0200,
> Christophe Leroy wrote:
> >
> >
> >
> > Le 28/06/2019 à 10:48, Takashi Iwai a écrit :
> > > On Thu, 27 Jun 2019 19:40:17 +0200,
> > > Fuqian Huang wrote:
> > >>
> > >> 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.
> > >>
> > >> Signed-off-by: Fuqian Huang <huangfq.daxian@gmail.com>
> > >
> > > Applied, thanks.
> > >
> >
> > Euh ... looks like a v2 of this series was sent out.
>
> OK, then I take back. Luckily, the tree wasn't pushed out yet.
> Thanks for the quick notice.
... and this turned out to be because of our mail server change.
Now I'm going to review & take v2 patches.
Takashi
prev parent reply other threads:[~2019-06-28 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 17:40 [PATCH 41/87] sound: ppc: remove memset after dma_alloc_coherent Fuqian Huang
2019-06-28 8:48 ` Takashi Iwai
2019-06-28 8:53 ` Christophe Leroy
2019-06-28 8:54 ` Takashi Iwai
2019-06-28 9:12 ` Takashi Iwai [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=s5himsq6pkp.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=christophe.leroy@c-s.fr \
--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=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;
as well as URLs for NNTP newsgroup(s).