QEMU-Riscv Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Alistair <alistair@alistair23.me>
Cc: Conor Dooley <conor@kernel.org>,
	 qemu-devel@nongnu.org, alistair23@gmail.com,
	 qemu-riscv@nongnu.org, bin.meng@processmission.com,
	 mzamazal@redhat.com,  mst@redhat.com, sgarzare@redhat.com
Subject: Re: [PATCH 1/2] MAINTAINERS: Mark "Microchip PolarFire SoC Icicle Kit" orphaned
Date: Tue, 14 Jul 2026 07:15:17 +0200	[thread overview]
Message-ID: <878q7ecftm.fsf@pond.sub.org> (raw)
In-Reply-To: <14e03e0ad01262333268b51efc512ae8d97d95f2.camel@alistair23.me> (alistair@alistair23.me's message of "Mon, 13 Jul 2026 09:46:39 +1000")

Alistair <alistair@alistair23.me> writes:

> On Sun, 2026-07-12 at 22:47 +0100, Conor Dooley wrote:
>> On Fri, Jul 10, 2026 at 01:43:04PM +0200, Markus Armbruster wrote:
>> > Commit 4a16a1a7ad (MAINTAINERS: Remove Bin Meng from RISC-V
>> > maintainers, 2025-01-28) removed the only M:, but left S:
>> > Supported.
>> > This makes no sense.  Downgrade to S: Orphan.
>> > 
>> > Signed-off-by: Markus Armbruster <armbru@redhat.com>
>> > ---
>> >  MAINTAINERS | 2 +-
>> >  1 file changed, 1 insertion(+), 1 deletion(-)
>> > 
>> > diff --git a/MAINTAINERS b/MAINTAINERS
>> > index 576ef6fff5..aa2df9cbe3 100644
>> > --- a/MAINTAINERS
>> > +++ b/MAINTAINERS
>> > @@ -1761,7 +1761,7 @@ F: tests/tcg/riscv64/test-crc32.S
>> >  
>> >  Microchip PolarFire SoC Icicle Kit
>> >  L: qemu-riscv@nongnu.org
>> > -S: Supported
>> > +S: Orphan
>> 
>> This should have been updated in:
>> https://lore.kernel.org/qemu-devel/20260513023859.518484-1-alistair.francis@wdc.com/
>> 
>> Alistair said he applied that patch, so I'm guessing whatever tree
>> you've
>> based on doesn't include it yet?
>
> Yeah, I thought I applied it. But somehow it seems to have
> disappeared....
>
>
> I think this patch should be dropped and I'll actually apply:
> https://lore.kernel.org/qemu-devel/20260513023859.518484-1-alistair.francis@wdc.com/

Makes sense, thanks!

> Then Bin can update this in the future if you want to.
>
> Sorry about the confusion here
>
> Alistair



  reply	other threads:[~2026-07-14  5:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10 11:43 [PATCH 0/2] MAINTAINERS: Mark sections orphaned Markus Armbruster
2026-07-10 11:43 ` [PATCH 1/2] MAINTAINERS: Mark "Microchip PolarFire SoC Icicle Kit" orphaned Markus Armbruster
2026-07-11 11:04   ` Bin Meng
2026-07-12 21:51     ` Conor Dooley
2026-07-12 23:21       ` Bin Meng
2026-07-13  6:06     ` Markus Armbruster
2026-07-12 21:47   ` Conor Dooley
2026-07-12 23:46     ` Alistair
2026-07-14  5:15       ` Markus Armbruster [this message]
2026-07-10 11:43 ` [PATCH 2/2] MAINTAINERS: Mark "vhost-user-scmi" orphaned Markus Armbruster
2026-07-11  8:00   ` Michael S. Tsirkin
2026-07-13  6:07     ` Markus Armbruster
2026-07-13  6:13     ` Philippe Mathieu-Daudé
2026-07-13  6:52       ` Michael S. Tsirkin
2026-07-13  7:11         ` Philippe Mathieu-Daudé
2026-07-13  7:16           ` Michael S. Tsirkin
2026-07-13  8:17           ` Markus Armbruster
2026-07-14 19:23             ` Michael S. Tsirkin
2026-07-15  6:16               ` 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=878q7ecftm.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alistair23@gmail.com \
    --cc=alistair@alistair23.me \
    --cc=bin.meng@processmission.com \
    --cc=conor@kernel.org \
    --cc=mst@redhat.com \
    --cc=mzamazal@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=sgarzare@redhat.com \
    /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