From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Kuan-Jui Chiu <kchiu@axiado.com>,
openbmc@lists.ozlabs.org, joel@jms.id.au
Subject: Re: [PATCH linux dev-6.12 v2 0/6] Add device tree for Axiado AX3000 EVK
Date: Mon, 12 Jan 2026 14:37:14 +1030 [thread overview]
Message-ID: <f43b8b95e96d34089282a1af2e26f3a6ee16fa36.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20c8a4e6-ef9c-452a-ab21-446e7de66d56@axiado.com>
On Mon, 2026-01-12 at 12:06 +0800, Kuan-Jui Chiu wrote:
> Hi Andrew
>
> I checked the 6.18 kernel and I found it had included all of the changes
> in this patch series already.
> So I believe we don't need this patch series anymore, thanks.
Great! Thanks for following up.
Andrew
prev parent reply other threads:[~2026-01-12 4:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 6:02 [PATCH linux dev-6.12 v2 0/6] Add device tree for Axiado AX3000 EVK Kuan-Jui Chiu
2026-01-09 6:02 ` [PATCH linux dev-6.12 v2 1/6] dt-bindings: gpio: cdns: convert to YAML Kuan-Jui Chiu
2026-01-09 6:02 ` [PATCH linux dev-6.12 v2 2/6] dt-bindings: gpio: cdns: add Axiado AX3000 GPIO variant Kuan-Jui Chiu
2026-01-09 6:02 ` [PATCH linux dev-6.12 v2 3/6] dt-bindings: serial: cdns: add Axiado AX3000 UART controller Kuan-Jui Chiu
2026-01-09 6:02 ` [PATCH linux dev-6.12 v2 4/6] dt-bindings: i3c: cdns: add Axiado AX3000 I3C controller Kuan-Jui Chiu
2026-01-09 6:02 ` [PATCH linux dev-6.12 v2 5/6] arm64: dts: axiado: Add initial support for AX3000 SoC and eval board Kuan-Jui Chiu
2026-01-09 6:02 ` [PATCH linux dev-6.12 v2 6/6] arm64: dts: axiado: Add missing UART aliases Kuan-Jui Chiu
2026-01-12 1:52 ` [PATCH linux dev-6.12 v2 0/6] Add device tree for Axiado AX3000 EVK Andrew Jeffery
2026-01-12 4:06 ` Kuan-Jui Chiu
2026-01-12 4:07 ` Andrew Jeffery [this message]
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=f43b8b95e96d34089282a1af2e26f3a6ee16fa36.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=kchiu@axiado.com \
--cc=openbmc@lists.ozlabs.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