From: Joerg Roedel <joro@8bytes.org>
To: Will Deacon <will@kernel.org>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
kernel-team@android.com, Robin Murphy <robin.murphy@arm.com>,
"Isaac J. Manjarres" <isaacm@codeaurora.org>,
Christoph Hellwig <hch@lst.de>,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
Rob Clark <robdclark@gmail.com>
Subject: Re: [PATCH] iommu: Remove unused IOMMU_SYS_CACHE_ONLY flag
Date: Fri, 10 Jul 2020 14:58:32 +0200 [thread overview]
Message-ID: <20200710125831.GI27672@8bytes.org> (raw)
In-Reply-To: <20200703162548.19953-1-will@kernel.org>
On Fri, Jul 03, 2020 at 05:25:48PM +0100, Will Deacon wrote:
> The IOMMU_SYS_CACHE_ONLY flag was never exposed via the DMA API and
> has no in-tree users. Remove it.
>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: "Isaac J. Manjarres" <isaacm@codeaurora.org>
> Cc: Joerg Roedel <joro@8bytes.org>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
> Cc: Rob Clark <robdclark@gmail.com>
> Signed-off-by: Will Deacon <will@kernel.org>
> ---
>
> As discussed in [1], sounds like this should be a domain attribute anyway
> when it's needed by the GPU.
>
> [1] https://lore.kernel.org/r/CAF6AEGsCROVTsi2R7_aUkmH9Luoc_guMR0w0KUJc2cEgpfj79w@mail.gmail.com
>
> drivers/iommu/io-pgtable-arm.c | 3 ---
> include/linux/iommu.h | 6 ------
> 2 files changed, 9 deletions(-)
Applied, thanks.
next prev parent reply other threads:[~2020-07-10 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 16:25 [PATCH] iommu: Remove unused IOMMU_SYS_CACHE_ONLY flag Will Deacon
2020-07-03 16:51 ` Sai Prakash Ranjan
2020-07-07 6:41 ` Christoph Hellwig
2020-07-10 12:58 ` Joerg Roedel [this message]
2020-07-10 13:05 ` Will Deacon
2020-07-10 14:15 ` Joerg Roedel
2020-07-10 14:37 ` Will Deacon
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=20200710125831.GI27672@8bytes.org \
--to=joro@8bytes.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=isaacm@codeaurora.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.com \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=will@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 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).