From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yu-Chun Lin <eleanor.lin@realtek.com>,
linux-kernel@vger.kernel.org,
linux-realtek-soc@lists.infradead.org, afaerber@suse.com,
arnd@arndb.de, alexandre.belloni@bootlin.com, linusw@kernel.org
Cc: fustini@kernel.org, cy.huang@realtek.com,
stanley_chang@realtek.com, james.tai@realtek.com,
linux-arm-kernel@lists.infradead.org, soc@lists.linux.dev
Subject: Re: [PATCH] arm64: dts: realtek: Fix memory node unit-address mismatch
Date: Wed, 18 Mar 2026 12:46:44 +0100 [thread overview]
Message-ID: <405a9783-0f77-4ce0-8288-43eaada09cff@kernel.org> (raw)
In-Reply-To: <20260318114047.2804171-1-eleanor.lin@realtek.com>
On 18/03/2026 12:40, Yu-Chun Lin wrote:
> The memory node unit-address should match the first address in the reg
> property. Correct the unit-address from @40000 to @50000 to align with the
> actual base address (0x50000) defined in the reg property.
>
> Fixes: b095c27fc874 ("arm64: dts: realtek: Add Kent SoC and EVB device trees")
> Signed-off-by: Yu-Chun Lin <eleanor.lin@realtek.com>
> ---
> This patch series is sent to both Realtek and ARM SoC maintainers.
> While Andreas Färber is listed as the Realtek maintainer, there has been
> limited activity recently.
Unfortunately nothing new, likely two years ago I was also complaining
on lack of maintenance on Realtek, but the solution is not to send
patches to soc@.
Solution to that would be to remove the platform, for example. Or work
on maintainership.
Did anyone from Realtek offered reviews to my patches posted 3 and 2
years ago? I don't see that.
Kent SoC was accepted under condition this will improve.
I drop this from soc patchwork and please do not send code for review
there, but either fix the lack of involvement from Realtek or let's drop
the platform if Realtek does not care.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-18 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 11:40 [PATCH] arm64: dts: realtek: Fix memory node unit-address mismatch Yu-Chun Lin
2026-03-18 11:46 ` Krzysztof Kozlowski [this message]
2026-03-18 14:28 ` Arnd Bergmann
2026-03-18 14:35 ` Krzysztof Kozlowski
2026-03-18 15:27 ` Andreas Färber
2026-03-18 17:20 ` Arnd Bergmann
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=405a9783-0f77-4ce0-8288-43eaada09cff@kernel.org \
--to=krzk@kernel.org \
--cc=afaerber@suse.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=cy.huang@realtek.com \
--cc=eleanor.lin@realtek.com \
--cc=fustini@kernel.org \
--cc=james.tai@realtek.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=soc@lists.linux.dev \
--cc=stanley_chang@realtek.com \
/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