From: Christoph Hellwig <hch@lst.de>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Paul Burton <paul.burton@mips.com>,
Christoph Hellwig <hch@lst.de>,
Kevin Cernekee <cernekee@gmail.com>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"iommu@lists.linux-foundation.org"
<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: Tue, 25 Sep 2018 22:05:43 +0200 [thread overview]
Message-ID: <20180925200542.GA8200@lst.de> (raw)
In-Reply-To: <62B54A6B-6E10-4A40-8E61-C1D23A853816@gmail.com>
On Sat, Sep 22, 2018 at 12:24:33PM -0700, Florian Fainelli wrote:
> >My thought would be that it would be ideal to fix in 4.19 since that's
> >where the breakage is, but having said that I don't have much insight
> >into how bad the breakage is for the affected systems.
>
>
> AFAIR, DMA corruption is typically what you would observe, which could prove difficult if you are not exactly looking for it. In any case, I don't have a BMIPS system running 4.19 right now to exercise this on, but this looks correct:
Well, I originally intended it for 4.19, but without reviews from
the affected maintainers I'd fell bad about it. Now that we've got
agreement I'll queue it for 4.19.
prev parent reply other threads:[~2018-09-25 20:05 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
2018-09-21 19:42 ` Paul Burton
2018-09-22 19:24 ` Florian Fainelli
2018-09-25 20:05 ` Christoph Hellwig [this message]
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=20180925200542.GA8200@lst.de \
--to=hch@lst.de \
--cc=cernekee@gmail.com \
--cc=f.fainelli@gmail.com \
--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