linux-kernel - Re: [PATCH 0/2] brcmstb-memc-ddr binding updates for MIPS boards

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aLHI7arPfcMDEhzM@alpha.franken.de>
Date: Fri, 29 Aug 2025 17:36:13 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Florian Fainelli <florian.fainelli@...adcom.com>,
	linux-mips@...r.kernel.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:MEMORY CONTROLLER DRIVERS" <linux-kernel@...r.kernel.org>,
	"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 0/2] brcmstb-memc-ddr binding updates for MIPS boards

On Fri, Aug 29, 2025 at 12:39:00PM +0200, Krzysztof Kozlowski wrote:
> On 29/08/2025 12:37, Krzysztof Kozlowski wrote:
> > On 29/08/2025 12:21, Thomas Bogendoerfer wrote:
> >> On Tue, Jul 29, 2025 at 01:52:11PM -0700, Florian Fainelli wrote:
> >>> This patch series updates the MIPS-based Broadcom STB chips to use a
> >>> proper compatible string for their memory controller node(s) after
> >>> 501be7cecec9 ("dt-bindings: memory-controller: Define fallback
> >>> compatible").
> >>>
> >>> Florian Fainelli (2):
> >>>   dt-bindings: memory: Update brcmstb-memc-ddr binding with older chips
> >>>   MIPS: BMIPS: Properly define memory controller compatible
> >>>
> >>>  .../bindings/memory-controllers/brcm,brcmstb-memc-ddr.yaml  | 4 ++++
> >>>  arch/mips/boot/dts/brcm/bcm7346.dtsi                        | 3 ++-
> >>>  arch/mips/boot/dts/brcm/bcm7360.dtsi                        | 3 ++-
> >>>  arch/mips/boot/dts/brcm/bcm7362.dtsi                        | 3 ++-
> >>>  arch/mips/boot/dts/brcm/bcm7425.dtsi                        | 6 ++++--
> >>>  arch/mips/boot/dts/brcm/bcm7435.dtsi                        | 6 ++++--
> >>>  6 files changed, 18 insertions(+), 7 deletions(-)
> >>
> >> series applied to mips-next.
> > 
> > Why entire series? You were notified two weeks ago that I already took
> > the driver subsystem patch.

I haven't got a mail in this thread from you about taking the first patch.

> ...and you do not have even ack from memory-controllers for that patch.

sorry, I'll drop the patch then.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]