mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Alex Deucher <alexander.deucher@amd.com>,
	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
Subject: Re: [PATCH V3 2/2] Documentation: x86: Clarify Intel IOMMU documentation
Date: Tue, 29 Mar 2022 13:38:26 +0700	[thread overview]
Message-ID: <57f74780-6520-f2a4-8551-74c4b0986ac6@gmail.com> (raw)
In-Reply-To: <20220328172829.718235-3-alexander.deucher@amd.com>

On 29/03/22 00.28, Alex Deucher wrote:
> Based on feedback from Robin on the initial AMD IOMMU
> documentation, fix up the Intel documentation to
> clarify IOMMU vs device and modern DMA API.
> 

Maybe we can squash into [1/2]?

-- 
An old man doll... just what I always wanted! - Clara

      reply	other threads:[~2022-03-29  6:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 17:28 [PATCH V3 0/2] x86 IOMMU Documentation updates Alex Deucher
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 [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=57f74780-6520-f2a4-8551-74c4b0986ac6@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=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®