All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jason Andryuk <jason.andryuk@amd.com>
Cc: xen-devel@lists.xenproject.org,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Anthony PERARD <anthony.perard@vates.tech>,
	Michal Orzel <michal.orzel@amd.com>,
	Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Add myself as an AMD SVM & IOMMU reviewer
Date: Fri, 3 Oct 2025 10:09:31 +0200	[thread overview]
Message-ID: <aN-EuzQ2AZ1oMN0K@Mac.lan> (raw)
In-Reply-To: <20251002234311.10926-1-jason.andryuk@amd.com>

On Thu, Oct 02, 2025 at 07:42:38PM -0400, Jason Andryuk wrote:
> Split out AMD SVM and AMD IOMMU, and add myself as a reviewer.  Jan,
> Andrew and Roger are set as maintainers as they were for the X86 entry.
> 
> Signed-off-by: Jason Andryuk <jason.andryuk@amd.com>

Thanks for adding yourself!

I have on question below about the mechanics of MAINTAINERS parsing
(but no objection at all with you becoming a reviewer).

> ---
>  MAINTAINERS | 20 +++++++++++++++++++-
>  1 file changed, 19 insertions(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 793561f63f..0139edd88b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -220,6 +220,23 @@ F:	xen/drivers/acpi/
>  F:	xen/include/acpi/
>  F:	tools/libacpi/
>  
> +AMD SVM
> +M:	Jan Beulich <jbeulich@suse.com>
> +M:	Andrew Cooper <andrew.cooper3@citrix.com>
> +M:	Roger Pau Monné <roger.pau@citrix.com>
> +R:	Jason Andryuk <jason.andryuk@amd.com>
> +S:	Supported
> +F:	xen/arch/x86/hvm/svm/
> +F:	xen/arch/x86/cpu/vpmu_amd.c
> +
> +AMD IOMMU
> +M:	Jan Beulich <jbeulich@suse.com>
> +M:	Andrew Cooper <andrew.cooper3@citrix.com>
> +M:	Roger Pau Monné <roger.pau@citrix.com>
> +R:	Jason Andryuk <jason.andryuk@amd.com>
> +S:	Supported
> +F:	xen/drivers/passthrough/amd/
> +
>  ARGO
>  M:	Christopher Clark <christopher.w.clark@gmail.com>
>  R:	Daniel P. Smith <dpsmith@apertussolutions.com>
> @@ -601,7 +618,8 @@ M:	Roger Pau Monné <roger.pau@citrix.com>
>  S:	Supported
>  L:	xen-devel@lists.xenproject.org
>  F:	xen/arch/x86/
> -F:	xen/drivers/passthrough/amd/
> +X:	xen/arch/x86/hvm/svm/
> +X:	xen/arch/x86/cpu/vpmu_amd.c

Would it be possible to not exclude the SVM related code here, and
avoid having to duplicate the x86 maintainers on the AMD entries?

Or the parsing of the file doesn't deal with multiple entries possibly
covering the same files?

Thanks, Roger.


  reply	other threads:[~2025-10-03  8:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 23:42 [PATCH] MAINTAINERS: Add myself as an AMD SVM & IOMMU reviewer Jason Andryuk
2025-10-03  8:09 ` Roger Pau Monné [this message]
2025-10-03  9:20   ` Anthony PERARD
2025-10-07 23:49     ` Jason Andryuk
2025-10-08  7:23       ` Roger Pau Monné
2025-10-07 14:14 ` Jan Beulich

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=aN-EuzQ2AZ1oMN0K@Mac.lan \
    --to=roger.pau@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=jason.andryuk@amd.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.