Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: linux-mips@linux-mips.org, paul.burton@mips.com
Cc: robin.murphy@arm.com, iommu@lists.linux-foundation.org
Subject: Re: [PATCH, for-4.19] dma-mapping: add the missing ARCH_HAS_SYNC_DMA_FOR_CPU_ALL declaration
Date: Fri, 21 Sep 2018 08:10:52 +0200	[thread overview]
Message-ID: <20180921061052.GA13705@lst.de> (raw)
In-Reply-To: <20180911090049.10747-1-hch@lst.de>

Paul, other mips folks, any comments?

At this point I'm tempted to just move it to 4.20 and add a stable
tag given that no one cared so far.

On Tue, Sep 11, 2018 at 11:00:49AM +0200, Christoph Hellwig wrote:
> The patch adding the infrastructure failed to actually add the symbol
> declaration, oops..
> 
> Fixes: faef87723a ("dma-noncoherent: add a arch_sync_dma_for_cpu_all hook")
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  kernel/dma/Kconfig | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/kernel/dma/Kconfig b/kernel/dma/Kconfig
> index 9bd54304446f..1b1d63b3634b 100644
> --- a/kernel/dma/Kconfig
> +++ b/kernel/dma/Kconfig
> @@ -23,6 +23,9 @@ config ARCH_HAS_SYNC_DMA_FOR_CPU
>  	bool
>  	select NEED_DMA_MAP_STATE
>  
> +config ARCH_HAS_SYNC_DMA_FOR_CPU_ALL
> +	bool
> +
>  config DMA_DIRECT_OPS
>  	bool
>  	depends on HAS_DMA
> -- 
> 2.18.0
> 
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
---end quoted text---

  parent reply	other threads:[~2018-09-21  6:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11  9:00 [PATCH, for-4.19] dma-mapping: add the missing ARCH_HAS_SYNC_DMA_FOR_CPU_ALL declaration Christoph Hellwig
2018-09-14 10:08 ` Christoph Hellwig
2018-09-14 15:44   ` Robin Murphy
2018-09-14 15:51     ` Christoph Hellwig
2018-09-21  6:10 ` Christoph Hellwig [this message]
2018-09-21 19:42   ` Paul Burton
2018-09-22 19:24     ` Florian Fainelli
2018-09-25 20:05       ` Christoph Hellwig

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=20180921061052.GA13705@lst.de \
    --to=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-mips@linux-mips.org \
    --cc=paul.burton@mips.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