[PATCH 0/4] Add AST2700 INTC0/INTC1 support

[Ryan Chen]

> Subject: Re: [PATCH 0/4] Add AST2700 INTC0/INTC1 support
> 
> 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.cam
> el at codeconstruct.com.au/
> [2]:
> https://lore.kernel.org/all/20251030060155.2342604-1-ryan_chen@aspeedtec
> h.com/

Hi Krzysztof,

    First of all, I would like to sincerely apologize for the confusion and extra burden.
    I recognize that I did not follow the upstream review process carefully enough,
    which made the series harder to review.
    I am now working with others to catch problems before sending changes to the lists
    and align with the community's expectations.

    Going forward, before sending a new revision, I will ensure that:

    * All review feedback is addressed explicitly,
     either through concrete changes or follow-up discussion that resolves the concern.
    * The series remains structured and traceable using b4.
    * Relevant tests are run and warnings/errors are addressed prior to posting.
    * A clearer internal checklist is followed before submission.

    The current subject line may have made it harder to relate this series to the previous discussion:
    https://lore.kernel.org/all/20250814-auspicious-thundering-jaybird-b76f4f@kuoka/

    To improve clarity and consistency across revisions,
    I will update the subject for this series to:

    "AST2700 interrupt controller hierarchy and route support"

    If you still see process issues, please let me know. I will correct them.

Best regards,
Ryan