From: Harshit Shah <hshah@axiado.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
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@lists.linux.dev>,
"soc@kernel.org" <soc@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] arm64: dts: axiado: Add missing UART aliases
Date: Fri, 29 Aug 2025 18:17:18 +0000 [thread overview]
Message-ID: <cb78b679-e349-43dc-a6ed-5b63b10d0d7f@axiado.com> (raw)
In-Reply-To: <4e51bbdc-744b-4a23-a695-a6c49d82e779@linaro.org>
On 8/28/2025 10:58 PM, Krzysztof Kozlowski wrote:
> 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
Hi Krzysztof,
Yes, the reason I have resent this patch with adding (soc@) as this is
the fix from the previous series.
Fixes: 1f7055779001 ("arm64: dts: axiado: Add initial support for AX3000 SoC and eval board")
I missed to add those aliases and it is giving probe failures without
these changes. So I was hoping if this could be merged as the fix
in the upcoming -rcX before the next merge window.
Regards,
Harshit.
next prev parent reply other threads:[~2025-08-29 18:17 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
2025-08-29 18:17 ` Harshit Shah [this message]
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=cb78b679-e349-43dc-a6ed-5b63b10d0d7f@axiado.com \
--to=hshah@axiado.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.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®