On Sat, Jul 11, 2026 at 07:04:14PM +0800, Bin Meng wrote:
> On Fri, Jul 10, 2026 at 7:44 PM Markus Armbruster <[email protected]> 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 <[email protected]>
> > ---
> >  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: [email protected]
> > -S: Supported
> > +S: Orphan
> >  F: docs/system/riscv/microchip-icicle-kit.rst
> >  F: hw/riscv/microchip_pfsoc.c
> >  F: hw/char/mchp_pfsoc_mmuart.c
> > --
> 
> I plan to send a patch series to resurrect PolarFire SoC support.

What does this resurrection constitute? The files aren't gone anywhere
(yet, at least), so I take it you mean you'll be actively working on the
platform?

Attachment: signature.asc
Description: PGP signature

Reply via email to