From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Ryan Chen <ryan_chen@aspeedtech.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Joel Stanley <joel@jms.id.au>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
Jeremy Kerr <jk@codeconstruct.com.au>
Subject: Re: [PATCH 0/4] Add AST2700 INTC0/INTC1 support
Date: Tue, 10 Feb 2026 17:55:58 +1030 [thread overview]
Message-ID: <feedc58438adad98f4b2a74a1499b2afa92a5eae.camel@codeconstruct.com.au> (raw)
In-Reply-To: <6de719dc84324166ed60bb8ec130cf2c9ef351f5.camel@codeconstruct.com.au>
Hi Krzysztof,
On Fri, 2026-02-06 at 17:49 +1030, Andrew Jeffery wrote:
> Is it acceptable if we take the following actions:
>
> 1. Do some b4 magic to transplant this series back onto [1]
> 2. Send a follow up revision with a link to this discussion in the
> cover letter
Following up my own post, I don't think we should attempt such
grafting. [1] references v4. v4 was superseded by v6 at [2], which was
merged.
Because of that merge, separating this proposal into a new series seems
warranted, but has the downside of making it difficult to compare to v4
of that earlier series.
I have gone through each of your feedback items from the earlier series
to consider recurring issues. Defining a new binding is unfortunate but
its addition side-steps an ABI break - perhaps rather than remove the
existing binding we can deprecate it, and keep the associated driver
(assuming this isn't overkill, given there are no in-tree users).
Otherwise it looks to me like the proposal has concerns covered, but
let me know if not.
Andrew
[1]: https://lore.kernel.org/all/1a2ca78746e00c2ec4bfc2953a897c48376ed36f.camel@codeconstruct.com.au/
[2]: https://lore.kernel.org/all/20251030060155.2342604-1-ryan_chen@aspeedtech.com/
next prev parent reply other threads:[~2026-02-10 7:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 6:07 [PATCH 0/4] Add AST2700 INTC0/INTC1 support Ryan Chen
2026-02-05 6:07 ` [PATCH 1/4] dt-bindings: interrupt-controller: aspeed: Add ASPEED AST2700 INTC0/INTC1 Ryan Chen
2026-02-05 7:25 ` Rob Herring (Arm)
2026-02-05 8:53 ` Krzysztof Kozlowski
2026-02-05 6:07 ` [PATCH 2/4] irqchip/ast2700-intcx: Add AST2700 INTC0/INTC1 support Ryan Chen
2026-02-05 14:40 ` kernel test robot
2026-02-05 14:52 ` kernel test robot
2026-02-06 11:34 ` Thomas Gleixner
2026-02-07 3:50 ` Ryan Chen
2026-02-07 12:40 ` Thomas Gleixner
2026-02-08 2:27 ` Ryan Chen
2026-02-05 6:07 ` [PATCH 3/4] irqchip/aspeed: Remove legacy AST2700 interrupt controller driver Ryan Chen
2026-02-05 6:07 ` [PATCH 4/4] dt-bindings: interrupt-controller: aspeed: Remove legacy AST2700 interrupt binding Ryan Chen
2026-02-05 8:56 ` Krzysztof Kozlowski
2026-02-05 8:58 ` [PATCH 0/4] Add AST2700 INTC0/INTC1 support Krzysztof Kozlowski
2026-02-05 9:49 ` Ryan Chen
2026-02-05 9:56 ` Krzysztof Kozlowski
2026-02-06 7:19 ` Andrew Jeffery
2026-02-10 7:25 ` Andrew Jeffery [this message]
2026-02-12 5:58 ` Ryan 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=feedc58438adad98f4b2a74a1499b2afa92a5eae.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=ryan_chen@aspeedtech.com \
--cc=tglx@linutronix.de \
/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