Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: linux-riscv@lists.infradead.org
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
	Emil Renner Berthing <kernel@esmil.dk>
Subject: [PATCH v1 2/4] MAINTAINERS: remove patchwork from RISC-V MISC SOC SUPPORT
Date: Sun, 23 Nov 2025 18:53:41 +0000	[thread overview]
Message-ID: <20251123-backroom-unshackle-21274947448d@spud> (raw)
In-Reply-To: <20251123-shopper-stunner-c3c5ff00b0ee@spud>

From: Conor Dooley <conor.dooley@microchip.com>

I don't use the main riscv patchwork for anything to do with SoCs,
remove them from here to avoid confusion.

Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
 MAINTAINERS | 1 -
 1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index a0e092d2d88a..0836b5422826 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -22117,7 +22117,6 @@ RISC-V MISC SOC SUPPORT
 M:	Conor Dooley <conor@kernel.org>
 L:	linux-riscv@lists.infradead.org
 S:	Maintained
-Q:	https://patchwork.kernel.org/project/linux-riscv/list/
 T:	git https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/
 F:	arch/riscv/boot/dts/canaan/
 F:	arch/riscv/boot/dts/microchip/
-- 
2.51.0


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2025-11-23 18:54 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 ` Conor Dooley [this message]
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
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=20251123-backroom-unshackle-21274947448d@spud \
    --to=conor@kernel.org \
    --cc=conor.dooley@microchip.com \
    --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