All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Zong-You Xie <ben717@andestech.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: <arnd@arndb.de>, <paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
	<aou@eecs.berkeley.edu>, <alex@ghiti.fr>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <tglx@linutronix.de>,
	<daniel.lezcano@linaro.org>,
	<prabhakar.mahadev-lad.rj@bp.renesas.com>,
	<devicetree@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <soc@lists.linux.dev>,
	<tim609@andestech.com>
Subject: Re: [PATCH 0/8] add Voyager board support
Date: Fri, 4 Jul 2025 21:07:05 +0800	[thread overview]
Message-ID: <aGfR+Vx0dseqgmKW@atctrx.andestech.com> (raw)
In-Reply-To: <cb8891d4-de4e-493c-9914-0391b3baf212@kernel.org>

On Fri, Jul 04, 2025 at 11:15:43AM +0200, Krzysztof Kozlowski wrote:
> > Also, there is a patch dependency in this patchset:
> > Patch 2 <- Patch 4 <- Patch 5 <- Patch 6
> 
> How? These are bindings. How DTS can depend on the binding? Do you have
> akcs from their subsystem maintainers that you are sending it here?
>
> Sorry, but no, this should go via their maintainers, unless they did not
> want to pick it up. Is this the case here?

The dependency chain arises because each of these patches introduces a new file,
requiring a corresponding update to the MAINTAINERS file.

In v4 [1], Rob and Daniel attempted to merge Patch 4 and Patch 5, respectively,
but encountered conflicts in the MAINTAINERS file. That's why I specified the
patch dependencies in v5 and this patchset.

Now, I understand that binding patches are typically handled by subsystem
maintainers. To prevent the conflicts again, I think I should gather all
MAINTAINERS file changes into a single patch. Is that right?

[1] https://lore.kernel.org/all/20250514095350.3765716-1-ben717@andestech.com/

Thanks,
Ben

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

WARNING: multiple messages have this Message-ID (diff)
From: Ben Zong-You Xie <ben717@andestech.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: <arnd@arndb.de>, <paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
	<aou@eecs.berkeley.edu>, <alex@ghiti.fr>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <tglx@linutronix.de>,
	<daniel.lezcano@linaro.org>,
	<prabhakar.mahadev-lad.rj@bp.renesas.com>,
	<devicetree@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <soc@lists.linux.dev>,
	<tim609@andestech.com>
Subject: Re: [PATCH 0/8] add Voyager board support
Date: Fri, 4 Jul 2025 21:07:05 +0800	[thread overview]
Message-ID: <aGfR+Vx0dseqgmKW@atctrx.andestech.com> (raw)
In-Reply-To: <cb8891d4-de4e-493c-9914-0391b3baf212@kernel.org>

On Fri, Jul 04, 2025 at 11:15:43AM +0200, Krzysztof Kozlowski wrote:
> > Also, there is a patch dependency in this patchset:
> > Patch 2 <- Patch 4 <- Patch 5 <- Patch 6
> 
> How? These are bindings. How DTS can depend on the binding? Do you have
> akcs from their subsystem maintainers that you are sending it here?
>
> Sorry, but no, this should go via their maintainers, unless they did not
> want to pick it up. Is this the case here?

The dependency chain arises because each of these patches introduces a new file,
requiring a corresponding update to the MAINTAINERS file.

In v4 [1], Rob and Daniel attempted to merge Patch 4 and Patch 5, respectively,
but encountered conflicts in the MAINTAINERS file. That's why I specified the
patch dependencies in v5 and this patchset.

Now, I understand that binding patches are typically handled by subsystem
maintainers. To prevent the conflicts again, I think I should gather all
MAINTAINERS file changes into a single patch. Is that right?

[1] https://lore.kernel.org/all/20250514095350.3765716-1-ben717@andestech.com/

Thanks,
Ben

  reply	other threads:[~2025-07-04 13:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-04  8:14 [PATCH 0/8] add Voyager board support Ben Zong-You Xie
2025-07-04  8:14 ` Ben Zong-You Xie
2025-07-04  8:14 ` [PATCH 1/8] riscv: add Andes SoC family Kconfig support Ben Zong-You Xie
2025-07-04  8:14   ` Ben Zong-You Xie
2025-07-07  9:50   ` Lad, Prabhakar
2025-07-07  9:50     ` Lad, Prabhakar
2025-07-11 10:51     ` Ben Zong-You Xie
2025-07-11 10:51       ` Ben Zong-You Xie
2025-07-04  8:14 ` [PATCH 2/8] dt-bindings: riscv: add Andes QiLai SoC and the Voyager board bindings Ben Zong-You Xie
2025-07-04  8:14   ` Ben Zong-You Xie
2025-07-04  8:14 ` [PATCH 3/8] dt-bindings: interrupt-controller: add Andes QiLai PLIC Ben Zong-You Xie
2025-07-04  8:14   ` Ben Zong-You Xie
2025-07-07  9:51   ` Lad, Prabhakar
2025-07-07  9:51     ` Lad, Prabhakar
2025-07-04  8:14 ` [PATCH 4/8] dt-bindings: interrupt-controller: add Andes machine-level software interrupt controller Ben Zong-You Xie
2025-07-04  8:14   ` Ben Zong-You Xie
2025-07-04  8:14 ` [PATCH 5/8] dt-bindings: timer: add Andes machine timer Ben Zong-You Xie
2025-07-04  8:14   ` Ben Zong-You Xie
2025-07-04  8:14 ` [PATCH 6/8] riscv: dts: andes: add QiLai SoC device tree Ben Zong-You Xie
2025-07-04  8:14   ` Ben Zong-You Xie
2025-07-04  8:14 ` [PATCH 7/8] riscv: dts: andes: add Voyager board " Ben Zong-You Xie
2025-07-04  8:14   ` Ben Zong-You Xie
2025-07-04  8:14 ` [PATCH 8/8] riscv: defconfig: enable Andes SoC Ben Zong-You Xie
2025-07-04  8:14   ` Ben Zong-You Xie
2025-07-04  9:15 ` [PATCH 0/8] add Voyager board support Krzysztof Kozlowski
2025-07-04  9:15   ` Krzysztof Kozlowski
2025-07-04 13:07   ` Ben Zong-You Xie [this message]
2025-07-04 13:07     ` Ben Zong-You Xie
2025-07-04 13:36     ` Arnd Bergmann
2025-07-04 13:36       ` Arnd Bergmann

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=aGfR+Vx0dseqgmKW@atctrx.andestech.com \
    --to=ben717@andestech.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=robh@kernel.org \
    --cc=soc@lists.linux.dev \
    --cc=tglx@linutronix.de \
    --cc=tim609@andestech.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.