From: Robin Murphy <robin.murphy@arm.com>
To: hch@lst.de, konrad.wilk@oracle.com
Cc: m.szyprowski@samsung.com, john.stultz@linaro.org,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, sstabellini@kernel.org
Subject: [PATCH v2 0/2] SWIOTLB fixes for 4.20
Date: Wed, 21 Nov 2018 16:00:49 +0000 [thread overview]
Message-ID: <cover.1542812807.git.robin.murphy@arm.com> (raw)
Here's a quick v2 addressing Christoph's nits and collecting the tags
given so far. I've reproduced my USB problem with a commit prior to the
dma-mapping pull, so it looks like the cache maintenance changes are off
the hook for that one (and I'll have to venture into USB/UAS territory).
No objection from me if Konrad wants to pick this up instead depending
on timing.
Robin.
Robin Murphy (2):
dma-direct: Make DIRECT_MAPPING_ERROR viable for SWIOTLB
swiotlb: Skip cache maintenance on map error
include/linux/dma-direct.h | 2 +-
kernel/dma/swiotlb.c | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
--
2.19.1.dirty
WARNING: multiple messages have this Message-ID (diff)
From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] SWIOTLB fixes for 4.20
Date: Wed, 21 Nov 2018 16:00:49 +0000 [thread overview]
Message-ID: <cover.1542812807.git.robin.murphy@arm.com> (raw)
Here's a quick v2 addressing Christoph's nits and collecting the tags
given so far. I've reproduced my USB problem with a commit prior to the
dma-mapping pull, so it looks like the cache maintenance changes are off
the hook for that one (and I'll have to venture into USB/UAS territory).
No objection from me if Konrad wants to pick this up instead depending
on timing.
Robin.
Robin Murphy (2):
dma-direct: Make DIRECT_MAPPING_ERROR viable for SWIOTLB
swiotlb: Skip cache maintenance on map error
include/linux/dma-direct.h | 2 +-
kernel/dma/swiotlb.c | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
--
2.19.1.dirty
next reply other threads:[~2018-11-21 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 16:00 Robin Murphy [this message]
2018-11-21 16:00 ` [PATCH v2 0/2] SWIOTLB fixes for 4.20 Robin Murphy
2018-11-21 16:00 ` [PATCH v2 1/2] dma-direct: Make DIRECT_MAPPING_ERROR viable for SWIOTLB Robin Murphy
2018-11-21 16:00 ` Robin Murphy
2018-11-21 16:00 ` [PATCH v2 2/2] swiotlb: Skip cache maintenance on map error Robin Murphy
2018-11-21 16:00 ` Robin Murphy
2018-11-27 20:38 ` Stefano Stabellini
2018-11-27 20:38 ` Stefano Stabellini
2018-11-21 17:49 ` [PATCH v2 0/2] SWIOTLB fixes for 4.20 Christoph Hellwig
2018-11-21 17:49 ` 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=cover.1542812807.git.robin.murphy@arm.com \
--to=robin.murphy@arm.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=john.stultz@linaro.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sstabellini@kernel.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 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.