From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Harshit Shah <hshah@axiado.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
soc@lists.linux.dev, soc@kernel.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] arm64: dts: axiado: Add missing UART aliases
Date: Fri, 29 Aug 2025 07:58:59 +0200 [thread overview]
Message-ID: <4e51bbdc-744b-4a23-a695-a6c49d82e779@linaro.org> (raw)
In-Reply-To: <20250828-axiado-ax3000-missing-serial-alias-v3-1-393111f4bd9e@axiado.com>
On 28/08/2025 20:27, Harshit Shah wrote:
> Axiado AX3000 EVK has total of 4 UART ports. Add missing alias for uart0,
> uart1, uart2.
>
> This fixes the probe failures on the remaining UARTs.
>
> Fixes: 1f7055779001 ("arm64: dts: axiado: Add initial support for AX3000 SoC and eval board")
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Harshit Shah <hshah@axiado.com>
> ---
> - Run "b4 trailes -u"
> - Link to v3: https://lore.kernel.org/r/20250824-axiado-ax3000-missing-serial-alias-v3-1-5db4143bf189@axiado.com
Please don't do this. It just generates unnecessary traffic. See my
instructions you receive on your first submissions.... unless you want
to send patches to soc@ (which looks added here) but then this is also
wrong - we do not send patch by patch. Collect *all* the patches for the
next merge window and send them around rc5 (rc6 being the latest).
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-29 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 18:27 Harshit Shah
2025-08-29 5:58 ` Krzysztof Kozlowski [this message]
2025-08-29 18:17 ` Harshit Shah
2025-08-30 9:12 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2025-08-24 14:56 Harshit Shah
2025-08-24 15:15 ` Krzysztof Kozlowski
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=4e51bbdc-744b-4a23-a695-a6c49d82e779@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hshah@axiado.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=soc@kernel.org \
--cc=soc@lists.linux.dev \
/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
all inboxes | Powered by JetHome®