From: Krzysztof Kozlowski <krzk@kernel.org>
To: Peter Chen <peter.chen@cixtech.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
catalin.marinas@arm.com, will@kernel.org, arnd@arndb.de
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, cix-kernel-upstream@cixtech.com,
maz@kernel.org, kajetan.puchalski@arm.com, sudeep.holla@arm.com,
eballetb@redhat.com, Fugang Duan <fugang.duan@cixtech.com>
Subject: Re: [PATCH v7 9/9] MAINTAINERS: Add CIX SoC maintainer entry
Date: Tue, 6 May 2025 20:38:45 +0200 [thread overview]
Message-ID: <2e0efc8f-516e-47fb-9a8f-f140bf8a47c9@kernel.org> (raw)
In-Reply-To: <20250506090752.3695666-10-peter.chen@cixtech.com>
On 06/05/2025 11:07, Peter Chen wrote:
> 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
next prev parent reply other threads:[~2025-05-06 18:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 9:07 [PATCH v7 0/9] arm64: Introduce CIX P1 (SKY1) SoC Peter Chen
2025-05-06 9:07 ` [PATCH v7 1/9] dt-bindings: vendor-prefixes: Add CIX Technology Group Co., Ltd Peter Chen
2025-05-06 9:07 ` [PATCH v7 2/9] dt-bindings: arm: add CIX P1 (SKY1) SoC Peter Chen
2025-05-06 9:07 ` [PATCH v7 3/9] arm64: Kconfig: add ARCH_CIX for cix silicons Peter Chen
2025-05-06 9:07 ` [PATCH v7 4/9] dt-bindings: mailbox: add cix,sky1-mbox Peter Chen
2025-05-06 9:07 ` [PATCH v7 5/9] mailbox: add CIX mailbox driver Peter Chen
2025-05-06 9:07 ` [PATCH v7 6/9] arm64: defconfig: Enable CIX SoC Peter Chen
2025-05-06 18:32 ` Krzysztof Kozlowski
2025-05-06 9:07 ` [PATCH v7 7/9] dt-bindings: clock: cix: Add CIX sky1 scmi clock id Peter Chen
2025-05-06 18:35 ` Krzysztof Kozlowski
2025-05-06 9:07 ` [PATCH v7 8/9] arm64: dts: cix: Add sky1 base dts initial support Peter Chen
2025-05-06 9:07 ` [PATCH v7 9/9] MAINTAINERS: Add CIX SoC maintainer entry Peter Chen
2025-05-06 18:38 ` Krzysztof Kozlowski [this message]
2025-05-07 1:42 ` Peter Chen
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=2e0efc8f-516e-47fb-9a8f-f140bf8a47c9@kernel.org \
--to=krzk@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eballetb@redhat.com \
--cc=fugang.duan@cixtech.com \
--cc=kajetan.puchalski@arm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=peter.chen@cixtech.com \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will@kernel.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