QEMU-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org,  "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>
Subject: Re: [PATCH] MAINTAINERS: Update RDMA migration entry with M:
Date: Tue, 12 May 2026 09:44:59 +0200	[thread overview]
Message-ID: <87y0hpysuc.fsf@pond.sub.org> (raw)
In-Reply-To: <20260511143026.1296485-1-peterx@redhat.com> (Peter Xu's message of "Mon, 11 May 2026 10:30:26 -0400")

Peter Xu <peterx@redhat.com> writes:

> We wanted to remove RDMA migration once but that didn't go further.  In
> reality, with the help of Zhijian it's in Odd Fixes stage, even if we just
> merged one new parameter for it, for performance improvements.
>
> Markus pointed out we'd better have at least one M: for it to match
> anything that is not orphaned.
>
> Remove the X: for Migration entry for RDMA files, then it'll start to cover
> RDMA migration again. Keep the separate entry so Zhijian can keep getting
> copied, and copy the M:s over to say someone is collecting patches.
> Logically these M:s aren't needed after removing X:, but make it clearer.
>
> Link: https://lore.kernel.org/r/5326b854-fcea-4af6-a479-792888a94a4d@fujitsu.com
> Cc: Zhijian Li (Fujitsu) <lizhijian@fujitsu.com>
> Cc: Markus Armbruster <armbru@redhat.com>
> Signed-off-by: Peter Xu <peterx@redhat.com>

Reviewed-by: Markus Armbruster <armbru@redhat.com>



  parent reply	other threads:[~2026-05-12  7:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 14:30 [PATCH] MAINTAINERS: Update RDMA migration entry with M: Peter Xu
2026-05-11 17:48 ` Peter Xu
2026-05-11 18:48 ` Fabiano Rosas
2026-05-12  7:44 ` Markus Armbruster [this message]
2026-05-13  7:41 ` Zhijian Li (Fujitsu)
2026-05-13 17:45 ` Markus Armbruster

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=87y0hpysuc.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=lizhijian@fujitsu.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.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