From: Sinan Kaya <Okaya@kernel.org>
To: Fuqian Huang <huangfq.daxian@gmail.com>
Cc: Andy Gross <agross@kernel.org>,
David Brown <david.brown@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v3 04/24] dmaengine: qcom_hidma: Remove call to memset after dmam_alloc_coherent
Date: Mon, 15 Jul 2019 11:17:07 -0400 [thread overview]
Message-ID: <245ffd79-316c-e985-d1da-2ccea6d29636@kernel.org> (raw)
In-Reply-To: <CABXRUiQXweOLRTpdyhx9xT_B1VBmoSoNm=_+Qr4prmz7u1QRFA@mail.gmail.com>
On 7/15/2019 1:43 AM, Fuqian Huang wrote:
> Should I rewrite the commit log? Just mention that dma_alloc_coherent
> has already
> zeroed the memory and not to reference the commit?
I'd like to hear from Robin Murphy that arm smmu driver follows this as
well.
WARNING: multiple messages have this Message-ID (diff)
From: Sinan Kaya <Okaya@kernel.org>
To: Fuqian Huang <huangfq.daxian@gmail.com>
Cc: linux-arm-msm@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
David Brown <david.brown@linaro.org>,
Vinod Koul <vkoul@kernel.org>, Andy Gross <agross@kernel.org>,
dmaengine@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 04/24] dmaengine: qcom_hidma: Remove call to memset after dmam_alloc_coherent
Date: Mon, 15 Jul 2019 11:17:07 -0400 [thread overview]
Message-ID: <245ffd79-316c-e985-d1da-2ccea6d29636@kernel.org> (raw)
In-Reply-To: <CABXRUiQXweOLRTpdyhx9xT_B1VBmoSoNm=_+Qr4prmz7u1QRFA@mail.gmail.com>
On 7/15/2019 1:43 AM, Fuqian Huang wrote:
> Should I rewrite the commit log? Just mention that dma_alloc_coherent
> has already
> zeroed the memory and not to reference the commit?
I'd like to hear from Robin Murphy that arm smmu driver follows this as
well.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-15 15:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 3:17 [PATCH v3 04/24] dmaengine: qcom_hidma: Remove call to memset after dmam_alloc_coherent Fuqian Huang
2019-07-15 3:17 ` Fuqian Huang
2019-07-15 4:17 ` Sinan Kaya
2019-07-15 4:17 ` Sinan Kaya
2019-07-15 5:43 ` Fuqian Huang
2019-07-15 5:43 ` Fuqian Huang
2019-07-15 15:17 ` Sinan Kaya [this message]
2019-07-15 15:17 ` Sinan Kaya
2019-07-16 11:35 ` Robin Murphy
2019-07-16 11:35 ` Robin Murphy
2019-07-16 15:10 ` Sinan Kaya
2019-07-16 15:10 ` Sinan Kaya
2019-08-08 12:22 ` Vinod Koul
2019-08-08 12:22 ` Vinod Koul
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=245ffd79-316c-e985-d1da-2ccea6d29636@kernel.org \
--to=okaya@kernel.org \
--cc=agross@kernel.org \
--cc=david.brown@linaro.org \
--cc=dmaengine@vger.kernel.org \
--cc=hch@infradead.org \
--cc=huangfq.daxian@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.