From: Paul Walmsley <pjw@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org,
Conor Dooley <conor.dooley@microchip.com>,
Emil Renner Berthing <kernel@esmil.dk>
Subject: Re: [PATCH v1 4/4] MAINTAINERS: degrade RISC-V MISC SOC SUPPORT to Odd Fixes
Date: Tue, 25 Nov 2025 02:58:59 -0700 (MST) [thread overview]
Message-ID: <129e2207-040e-9eaa-9e81-b145e18182ed@kernel.org> (raw)
In-Reply-To: <20251123-reactor-jubilant-36551b0d8143@spud>
On Sun, 23 Nov 2025, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> The SiFive and Canaan platforms are not being actively looked after at
> this point, but fixes for them would be applied if/when the patches
> appeared. Since they're now the only things in the RISC-V MISC SOC
> SUPPORT, mark them as Odd Fixes. I don't believe this is a functional
> change, it just represents what's actually happening - particularly
> since the Canaan k230 never built up enough steam to get merged and the
> new SiFive demo chips have been done in partnership with with other
> companies, e.g. Eswin, and will reside in their directories instead.
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
Reviewed-by: Paul Walmsley <pjw@kernel.org>
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-11-25 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 18:53 [PATCH v1 1/4] MAINTAINERS: add Conor to StarFive entry Conor Dooley
2025-11-23 18:53 ` [PATCH v1 2/4] MAINTAINERS: remove patchwork from RISC-V MISC SOC SUPPORT Conor Dooley
2025-11-23 18:53 ` [PATCH v1 3/4] MAINTAINERS: add tree to RISC-V Microchip entry Conor Dooley
2025-11-23 18:53 ` [PATCH v1 4/4] MAINTAINERS: degrade RISC-V MISC SOC SUPPORT to Odd Fixes Conor Dooley
2025-11-25 9:58 ` Paul Walmsley [this message]
2025-11-24 12:19 ` [PATCH v1 1/4] MAINTAINERS: add Conor to StarFive entry Emil Renner Berthing
2025-11-25 22:24 ` Conor Dooley
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=129e2207-040e-9eaa-9e81-b145e18182ed@kernel.org \
--to=pjw@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=kernel@esmil.dk \
--cc=linux-riscv@lists.infradead.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