All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Christoph Hellwig <hch@lst.de>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org,
	Ren Zhijie <renzhijie2@huawei.com>,
	robin.murphy@arm.com, mark-pk.tsai@mediatek.com
Subject: Re: [PATCH -next] dma-mapping: Fix build error unused-value
Date: Mon, 4 Jul 2022 09:53:37 -0600	[thread overview]
Message-ID: <20220704155337.GA2375750@p14s> (raw)
In-Reply-To: <20220630143116.GA6198@lst.de>

On Thu, Jun 30, 2022 at 04:31:16PM +0200, Christoph Hellwig wrote:
> 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")
>

I fixed the missing space and applied this patch.

Thanks,
Mathieu

> missing space before the opening brace here.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Ren Zhijie <renzhijie2@huawei.com>,
	m.szyprowski@samsung.com, robin.murphy@arm.com,
	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: Mon, 4 Jul 2022 09:53:37 -0600	[thread overview]
Message-ID: <20220704155337.GA2375750@p14s> (raw)
Message-ID: <20220704155337.mzxA-N_4HkQ3T4aZg8z9tIoR-h8hTjvyLEm3_Ad1NTE@z> (raw)
In-Reply-To: <20220630143116.GA6198@lst.de>

On Thu, Jun 30, 2022 at 04:31:16PM +0200, Christoph Hellwig wrote:
> 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")
>

I fixed the missing space and applied this patch.

Thanks,
Mathieu

> missing space before the opening brace here.

  reply	other threads:[~2022-07-04 15:53 UTC|newest]

Thread overview: 6+ 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 via iommu
2022-06-30 12:35 ` Ren Zhijie
2022-06-30 14:31 ` Christoph Hellwig
2022-06-30 14:31   ` Christoph Hellwig
2022-07-04 15:53   ` Mathieu Poirier [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=20220704155337.GA2375750@p14s \
    --to=mathieu.poirier@linaro.org \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=iommu@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark-pk.tsai@mediatek.com \
    --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 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.