mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: "T.J. Mercier" <tjmercier@google.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: petr@tesarici.cz, mhklinux@outlook.com, robin.murphy@arm.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] doc: swiotlb: iommu/dma: Clarify swiotlb=force option applies only to dma-direct
Date: Thu, 9 May 2024 13:18:02 -0700	[thread overview]
Message-ID: <2125dda3-829c-4113-988c-3c5861127f97@intel.com> (raw)
In-Reply-To: <20240507013502.3095744-1-tjmercier@google.com>

So, I know get_maintainer.pl doesn't work great for files that are used
by a lot of subsystems, but it doesn't seem _super_ hard to find
relevant maintainers for this stuff.

There are many IOMMU and swiotlb folks in MAINTAINERS who aren't cc'd
here.  I'd be great to get an ack from those folks.
iommu@lists.linux.dev seems to pop up pretty frequently.

I'd also have zero objections to a patch to:

	Documentation/arch/x86/x86_64/boot-options.rst

that goes through another tree.

  parent reply	other threads:[~2024-05-09 20:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07  1:34 T.J. Mercier
2024-05-07  1:34 ` [PATCH v2 2/3] doc: swiotlb: Document SWIOTLB areas parameter T.J. Mercier
2024-05-09  6:14   ` Petr Tesařík
2024-05-09 16:04     ` T.J. Mercier
2024-05-09 20:01       ` Petr Tesařík
2024-05-07  1:35 ` [PATCH v2 3/3] doc: x86/iommu: Update and reorder iommu options T.J. Mercier
2024-05-09  5:52 ` [PATCH v2 1/3] doc: swiotlb: iommu/dma: Clarify swiotlb=force option applies only to dma-direct Petr Tesařík
2024-05-09 20:18 ` Dave Hansen [this message]
2024-05-09 21:03   ` T.J. Mercier

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=2125dda3-829c-4113-988c-3c5861127f97@intel.com \
    --to=dave.hansen@intel.com \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhklinux@outlook.com \
    --cc=mingo@redhat.com \
    --cc=petr@tesarici.cz \
    --cc=robin.murphy@arm.com \
    --cc=tglx@linutronix.de \
    --cc=tjmercier@google.com \
    --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®