All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>
Cc: linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
	devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
	Saravana Kannan <saravanak@google.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Hanjun Guo <guohanjun@huawei.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>,
	Jean-Philippe Brucker <jean-philippe@linaro.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: [PATCH v2 0/4] iommu: Remove iommu_fwspec ops
Date: Fri, 21 Jun 2024 19:46:35 +0100	[thread overview]
Message-ID: <cover.1718994350.git.robin.murphy@arm.com> (raw)

v1: https://lore.kernel.org/linux-iommu/cover.1713523251.git.robin.murphy@arm.com

Hi all,

Here's v2 of this little cleanup, with acks and the additional cosmetic
tweak suggested by Andy. There were some slightly non-trivial changes in
the rebase so I've left off Jean-Philippe's tested-by from v1, but I've
given it a quick spin on arm64 ACPI and DT and all seems well still.

Thanks,
Robin.


Robin Murphy (4):
  iommu: Resolve fwspec ops automatically
  ACPI: Retire acpi_iommu_fwspec_ops()
  OF: Simplify of_iommu_configure()
  iommu: Remove iommu_fwspec ops

 drivers/acpi/arm64/iort.c             | 19 +++-------
 drivers/acpi/scan.c                   | 36 +++++--------------
 drivers/acpi/viot.c                   | 11 ++----
 drivers/iommu/arm/arm-smmu/arm-smmu.c |  3 +-
 drivers/iommu/iommu-priv.h            |  7 ++++
 drivers/iommu/iommu.c                 | 20 +++++------
 drivers/iommu/mtk_iommu_v1.c          |  2 +-
 drivers/iommu/of_iommu.c              | 50 ++++++++++-----------------
 drivers/iommu/tegra-smmu.c            |  2 +-
 drivers/of/device.c                   | 30 ++++++----------
 include/acpi/acpi_bus.h               |  3 +-
 include/linux/iommu.h                 | 15 ++------
 12 files changed, 65 insertions(+), 133 deletions(-)

-- 
2.39.2.101.g768bb238c484.dirty


             reply	other threads:[~2024-06-21 18:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 18:46 Robin Murphy [this message]
2024-06-21 18:46 ` [PATCH v2 1/4] iommu: Resolve fwspec ops automatically Robin Murphy
2024-06-21 18:46 ` [PATCH v2 2/4] ACPI: Retire acpi_iommu_fwspec_ops() Robin Murphy
2024-06-21 18:46 ` [PATCH v2 3/4] OF: Simplify of_iommu_configure() Robin Murphy
2024-06-22 22:23   ` Andy Shevchenko
2024-06-25 18:44     ` Robin Murphy
2024-06-21 18:46 ` [PATCH v2 4/4] iommu: Remove iommu_fwspec ops Robin Murphy
2024-07-01 20:37   ` kernel test robot
2024-06-21 20:51 ` [PATCH v2 0/4] " Saravana Kannan
2024-07-02 12:23   ` Robin Murphy
2024-07-01 13:49 ` Jean-Philippe Brucker

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.1718994350.git.robin.murphy@arm.com \
    --to=robin.murphy@arm.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=guohanjun@huawei.com \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.org \
    --cc=joro@8bytes.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=saravanak@google.com \
    --cc=sudeep.holla@arm.com \
    --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 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.