From: Christoph Hellwig <hch@lst.de>
To: Ren Zhijie <renzhijie2@huawei.com>
Cc: hch@lst.de, m.szyprowski@samsung.com, robin.murphy@arm.com,
mathieu.poirier@linaro.org, mark-pk.tsai@mediatek.com,
iommu@lists.linux-foundation.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] dma-mapping: Fix build error unused-value
Date: Thu, 30 Jun 2022 16:31:16 +0200 [thread overview]
Message-ID: <20220630143116.GA6198@lst.de> (raw)
In-Reply-To: <20220630123528.251181-1-renzhijie2@huawei.com>
Thanks, this looks good with a minor nit below:
Reviewed-by: Christoph Hellwig <hch@lst.de>
Mathieu, can you pick this up through your tree as that is where the
offending commit was merged through?
> Fixes: e61c451476e6("dma-mapping: Add dma_release_coherent_memory to DMA API")
missing space before the opening brace here.
next prev parent reply other threads:[~2022-06-30 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 12:35 [PATCH -next] dma-mapping: Fix build error unused-value Ren Zhijie
2022-06-30 14:31 ` Christoph Hellwig [this message]
2022-07-04 15:53 ` Mathieu Poirier
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=20220630143116.GA6198@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mark-pk.tsai@mediatek.com \
--cc=mathieu.poirier@linaro.org \
--cc=renzhijie2@huawei.com \
--cc=robin.murphy@arm.com \
/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