From: Joerg Roedel <joro@8bytes.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: will@kernel.org, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] iommu: Split out and tidy up Arm Kconfig
Date: Thu, 17 Apr 2025 16:34:37 +0200 [thread overview]
Message-ID: <aAERfYNxHvezN5XC@8bytes.org> (raw)
In-Reply-To: <a614ec86ba78c09cd16e348f633f6bb38793391f.1742480488.git.robin.murphy@arm.com>
On Thu, Mar 20, 2025 at 02:21:28PM +0000, Robin Murphy wrote:
> drivers/iommu/Kconfig | 157 +-------------------------------------
> drivers/iommu/arm/Kconfig | 144 ++++++++++++++++++++++++++++++++++
> 2 files changed, 145 insertions(+), 156 deletions(-)
> create mode 100644 drivers/iommu/arm/Kconfig
Applied, thanks.
prev parent reply other threads:[~2025-04-17 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 14:21 [PATCH] iommu: Split out and tidy up Arm Kconfig Robin Murphy
2025-03-21 7:18 ` Pranjal Shrivastava
2025-03-21 11:35 ` Robin Murphy
2025-04-17 14:34 ` Joerg Roedel [this message]
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=aAERfYNxHvezN5XC@8bytes.org \
--to=joro@8bytes.org \
--cc=geert+renesas@glider.be \
--cc=iommu@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robin.murphy@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 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).