From: Christoph Hellwig <hch@infradead.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: catalin.marinas@arm.com, joro@8bytes.org, will.deacon@arm.com,
linuxarm@huawei.com, iommu@lists.linux-foundation.org,
guohanjun@huawei.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] iommu: Avoid DMA ops domain refcount contention
Date: Fri, 17 Aug 2018 00:24:15 -0700 [thread overview]
Message-ID: <20180817072415.GA22241@infradead.org> (raw)
In-Reply-To: <cover.1534250425.git.robin.murphy@arm.com>
I plan to make the arm iommu dma ops generic and move them to
drivers/iommu for the 4.20 merge window. Because of that it would
be great to create a stable branch or even pull this in through
the dma-mapping tree entirely.
WARNING: multiple messages have this Message-ID (diff)
From: hch@infradead.org (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] iommu: Avoid DMA ops domain refcount contention
Date: Fri, 17 Aug 2018 00:24:15 -0700 [thread overview]
Message-ID: <20180817072415.GA22241@infradead.org> (raw)
In-Reply-To: <cover.1534250425.git.robin.murphy@arm.com>
I plan to make the arm iommu dma ops generic and move them to
drivers/iommu for the 4.20 merge window. Because of that it would
be great to create a stable branch or even pull this in through
the dma-mapping tree entirely.
next prev parent reply other threads:[~2018-08-17 7:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 13:04 [PATCH 0/3] iommu: Avoid DMA ops domain refcount contention Robin Murphy
2018-08-14 13:04 ` Robin Murphy
[not found] ` <cover.1534250425.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2018-08-14 13:04 ` [PATCH 1/3] iommu: Add fast hook for getting DMA domains Robin Murphy
2018-08-14 13:04 ` Robin Murphy
2018-08-17 9:36 ` John Garry
2018-08-17 9:36 ` John Garry
[not found] ` <d31ca4b3-5cb3-8ba3-485b-3fee58807cae-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-08-17 11:11 ` Robin Murphy
2018-08-17 11:11 ` Robin Murphy
[not found] ` <4d50587e62c16f7b5cfc45dee808d774655155cf.1534250425.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2018-08-17 15:27 ` Laurentiu Tudor
2018-08-17 15:27 ` Laurentiu Tudor
2018-08-14 13:04 ` [PATCH 2/3] iommu/dma: Use fast DMA domain lookup Robin Murphy
2018-08-14 13:04 ` Robin Murphy
2018-08-14 13:04 ` [PATCH 3/3] arm64/dma-mapping: Mildly optimise non-coherent IOMMU ops Robin Murphy
2018-08-14 13:04 ` Robin Murphy
[not found] ` <52b017ead032f90e5f2b70b87747a49eb86209c8.1534250425.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2018-08-20 15:41 ` Robin Murphy
2018-08-20 15:41 ` Robin Murphy
2018-08-14 13:38 ` [PATCH 0/3] iommu: Avoid DMA ops domain refcount contention John Garry
2018-08-14 13:38 ` John Garry
2018-08-17 13:03 ` John Garry
2018-08-17 13:03 ` John Garry
2018-08-17 7:24 ` Christoph Hellwig [this message]
2018-08-17 7:24 ` Christoph Hellwig
[not found] ` <20180817072415.GA22241-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2018-08-17 9:03 ` Will Deacon
2018-08-17 9:03 ` Will Deacon
2018-08-17 11:30 ` Robin Murphy
2018-08-17 11:30 ` Robin Murphy
2018-08-17 12:01 ` Christoph Hellwig
2018-08-17 12:01 ` 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=20180817072415.GA22241@infradead.org \
--to=hch@infradead.org \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=robin.murphy@arm.com \
--cc=will.deacon@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 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.