From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Robin Murphy <robin.murphy@arm.com>,
m.szyprowski@samsung.com, john.stultz@linaro.org,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] SWIOTLB fixes for 4.20
Date: Tue, 20 Nov 2018 11:34:41 -0500 [thread overview]
Message-ID: <20181120163441.GD31199@char.us.oracle.com> (raw)
In-Reply-To: <20181120160818.GC2492@lst.de>
On Tue, Nov 20, 2018 at 05:08:18PM +0100, Christoph Hellwig wrote:
> On Tue, Nov 20, 2018 at 02:09:51PM +0000, Robin Murphy wrote:
> > This is what I have so far, which at least resolves the most ovbious
> > problems. I still haven't got very far with the USB corruption issue
> > I see on Juno with -rc1, but I'm yet to confirm whether that's actually
> > attributable to the SWIOTLB changes or something else entirely.
>
> This looks good modulo the minor nitpicks.
>
> Konrad, are you ok with me picking up both through the dma-mapping
> tree?
Yes, albeit I would want Stefano to take a peek at patch #2 just in case.
next prev parent reply other threads:[~2018-11-20 16:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 14:09 [PATCH 0/2] SWIOTLB fixes for 4.20 Robin Murphy
2018-11-20 14:09 ` [PATCH 1/2] swiotlb: Make DIRECT_MAPPING_ERROR viable Robin Murphy
2018-11-20 14:49 ` Konrad Rzeszutek Wilk
2018-11-20 15:01 ` Robin Murphy
2018-11-20 16:34 ` Konrad Rzeszutek Wilk
2018-11-20 16:07 ` Christoph Hellwig
2018-11-20 14:09 ` [PATCH 2/2] swiotlb: Skip cache maintenance on map error Robin Murphy
2018-11-20 14:49 ` Konrad Rzeszutek Wilk
2018-11-20 16:07 ` Christoph Hellwig
2018-11-20 16:08 ` [PATCH 0/2] SWIOTLB fixes for 4.20 Christoph Hellwig
2018-11-20 16:34 ` Konrad Rzeszutek Wilk [this message]
2018-11-21 13:03 ` Christoph Hellwig
2018-11-21 15:11 ` Konrad Rzeszutek Wilk
2018-11-27 19:07 ` Stefano Stabellini
2018-11-27 20:39 ` Stefano Stabellini
2018-11-20 19:24 ` John Stultz
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=20181120163441.GD31199@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.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;
as well as URLs for NNTP newsgroup(s).