public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-realtek-soc@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH] arm64: dts: realtek: align UART node name with bindings
Date: Fri, 27 Jan 2023 13:22:44 +0100	[thread overview]
Message-ID: <a3ca0bd8-2153-cf69-adf3-bc92a31d0efb@suse.de> (raw)
In-Reply-To: <167481277324.62929.7688485206150758782.b4-ty@linaro.org>

On 27.01.23 10:46, Krzysztof Kozlowski wrote:
> On Mon, 23 Jan 2023 16:15:14 +0100, Krzysztof Kozlowski wrote:
>> Bindings expect UART/serial node names to be "serial".
> 
> Applied, thanks!
> 
> Let me know if anyone preferred to take it via sub-arch/SoC maintainer tree.
> I'll drop it then.

We did have an equivalent patch in '21, from Zhen Lei of Huawei, that I 
gave a Reviewed-by for. So should you maybe apply that original patch 
instead?

Reminder: My Realtek testing broke when someone removed upstream support 
for adjusting the text offset (they have a boot ROM at start of memory).

Regards,
Andreas

> 
> [1/1] arm64: dts: realtek: align UART node name with bindings
>        https://git.kernel.org/krzk/linux-dt/c/5ad30c5fc0a72c2aaa1d26f9e4061d8646231adb
> 
> Best regards,

-- 
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nürnberg)


  reply	other threads:[~2023-01-27 12:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 15:15 [PATCH] arm64: dts: realtek: align UART node name with bindings Krzysztof Kozlowski
2023-01-27  9:46 ` Krzysztof Kozlowski
2023-01-27 12:22   ` Andreas Färber [this message]
2023-01-27 12:27     ` 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=a3ca0bd8-2153-cf69-adf3-bc92a31d0efb@suse.de \
    --to=afaerber@suse.de \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-realtek-soc@lists.infradead.org \
    --cc=robh+dt@kernel.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