From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Cc: linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
paul.burton-8NJIiSa5LzA@public.gmane.org,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Subject: Re: [PATCH, for-4.19] dma-mapping: add the missing ARCH_HAS_SYNC_DMA_FOR_CPU_ALL declaration
Date: Fri, 14 Sep 2018 17:51:50 +0200 [thread overview]
Message-ID: <20180914155150.GA30438@lst.de> (raw)
In-Reply-To: <00257a79-72cf-15aa-fed9-d75923eed51e-5wv7dgnIgG8@public.gmane.org>
On Fri, Sep 14, 2018 at 04:44:15PM +0100, Robin Murphy wrote:
> On 14/09/18 11:08, Christoph Hellwig wrote:
>> Aby chance to get a review for this?
>
> So without this, the select does nothing,
> CONFIG_ARCH_HAS_SYNC_DMA_FOR_CPU_ALL is never defined, and BMIPS gets the
> static inline stub and never flushes the RAC when it should?
Exactly!
next prev parent reply other threads:[~2018-09-14 15:51 UTC|newest]
Thread overview: 7+ 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
[not found] ` <20180911090049.10747-1-hch-jcswGhMUV9g@public.gmane.org>
2018-09-14 10:08 ` Christoph Hellwig
[not found] ` <20180914100842.GA23696-jcswGhMUV9g@public.gmane.org>
2018-09-14 15:44 ` Robin Murphy
[not found] ` <00257a79-72cf-15aa-fed9-d75923eed51e-5wv7dgnIgG8@public.gmane.org>
2018-09-14 15:51 ` Christoph Hellwig [this message]
[not found] ` <20180921061052.GA13705@lst.de>
[not found] ` <20180921061052.GA13705-jcswGhMUV9g@public.gmane.org>
2018-09-21 19:42 ` Paul Burton
2018-09-22 19:24 ` Florian Fainelli
[not found] ` <62B54A6B-6E10-4A40-8E61-C1D23A853816-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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=20180914155150.GA30438@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org \
--cc=paul.burton-8NJIiSa5LzA@public.gmane.org \
--cc=robin.murphy-5wv7dgnIgG8@public.gmane.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 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).