From: Alex Deucher <alexander.deucher@amd.com>
To: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<corbet@lwn.net>, <hpa@zytor.com>, <x86@kernel.org>,
<dave.hansen@linux.intel.com>, <bp@alien8.de>, <mingo@redhat.com>,
<tglx@linutronix.de>, <joro@8bytes.org>,
<suravee.suthikulpanit@amd.com>, <will@kernel.org>,
<iommu@lists.linux-foundation.org>, <robin.murphy@arm.com>,
<vasant.hegde@amd.com>
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: [PATCH V3 0/2] x86 IOMMU Documentation updates
Date: Mon, 28 Mar 2022 13:28:27 -0400 [thread overview]
Message-ID: <20220328172829.718235-1-alexander.deucher@amd.com> (raw)
This was originally just a patch to add an AMD IOMMU
documentation page, but grew into some cleanup of the
Intel IOMMU documentation page.
v2: AMD documentation rework
Add Intel Updates
v3: Further documentation reworks
Alex Deucher (2):
Documentation: x86: Add documentation for AMD IOMMU
Documentation: x86: Clarify Intel IOMMU documentation
Documentation/x86/amd-iommu.rst | 69 +++++++++++++++++++++++++++++++
Documentation/x86/index.rst | 1 +
Documentation/x86/intel-iommu.rst | 13 +++---
3 files changed, 76 insertions(+), 7 deletions(-)
create mode 100644 Documentation/x86/amd-iommu.rst
--
2.35.1
next reply other threads:[~2022-03-28 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 17:28 Alex Deucher [this message]
2022-03-28 17:28 ` [PATCH V3 1/2] Documentation: x86: Add documentation for AMD IOMMU Alex Deucher
2022-03-29 15:24 ` Dave Hansen
2022-03-30 14:01 ` Deucher, Alexander
2022-03-30 14:20 ` Dave Hansen
2022-03-28 17:28 ` [PATCH V3 2/2] Documentation: x86: Clarify Intel IOMMU documentation Alex Deucher
2022-03-29 6:38 ` Bagas Sanjaya
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=20220328172829.718235-1-alexander.deucher@amd.com \
--to=alexander.deucher@amd.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®