[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMuHMdXjYJeS48jToVe9O8DsadyeT0q1CsBxQtx3k+X5h8LLTg@mail.gmail.com>
Date: Fri, 27 Jun 2025 13:28:01 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Florian Fainelli <florian.fainelli@...adcom.com>
Cc: linux-kernel@...r.kernel.org, Krzysztof Kozlowski <krzk@...nel.org>,
Rob Herring <robh@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree@...r.kernel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE" <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: memory-controller: Define fallback compatible
Hi Florian,
On Tue, 10 Jun 2025 at 16:32, Florian Fainelli
<florian.fainelli@...adcom.com> wrote:
> All of the DDR controllers beyond revision b.2.1 have had a consistent
> layout, therefore define a "brcm,brcmstb-memc-ddr-rev-b.2.1" fallback
> compatible string to match them all rather than having to continuously
> add to the list.
>
> Link: https://lore.kernel.org/all/20241217194439.929040-2-florian.fainelli@broadcom.com/
> Signed-off-by: Florian Fainelli <florian.fainelli@...adcom.com>
Thanks for your patch, which is now commit 501be7cecec9aaf9
("dt-bindings: memory-controller: Define fallback compatible")
in mem-ctrl/for-next
> .../brcm,brcmstb-memc-ddr.yaml | 54 ++++++++++++-------
The oneline-summary really needs a "brcm" part, as this does
not apply to all memory controllers.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists