Thread (14 messages) 14 messages, 2 authors, 2025-05-07

Re: [PATCH v7 9/9] MAINTAINERS: Add CIX SoC maintainer entry

From: Krzysztof Kozlowski <krzk@kernel.org>
Date: 2025-05-06 18:38:51
Also in: linux-devicetree, lkml

On 06/05/2025 11:07, Peter Chen wrote:
quoted hunk ↗ jump to hunk
Using this entry as the maintainers information for CIX SoCs.

Acked-by: Fugang Duan <fugang.duan@cixtech.com>
Signed-off-by: Peter Chen <peter.chen@cixtech.com>
---
 MAINTAINERS | 11 +++++++++++
 1 file changed, 11 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c59316109e3f..169b89eabea3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2404,6 +2404,17 @@ F:	arch/arm/boot/compressed/misc-ep93xx.h
 F:	arch/arm/mach-ep93xx/
 F:	drivers/iio/adc/ep93xx_adc.c
 
+ARM/CIX SOC SUPPORT
+M:	Peter Chen <peter.chen@cixtech.com>
+M:	Fugang Duan <fugang.duan@cixtech.com>
+R:	CIX Linux Kernel Upstream Group <cix-kernel-upstream@cixtech.com>
+L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
+S:	Maintained
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/cix.git
I am confused. I see this patchset already applied (3 weeks ago!) to
above git repo:
https://web.git.kernel.org/pub/scm/linux/kernel/git/peter.chen/cix.git/log/?h=cix-for-next

in a branch claiming this is for the next. This is the branch which you
are supposed to be feeding next, so:
1. Are you properly feeding linux-next (see for example my beginners
talk from 2023 plumbers how to do it)?

2. If so, how can you send something for review - v7 - while this is
already applied and scheduled for next cycle (that is the meaning of
"for-next")?

Best regards,
Krzysztof
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help