From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
linux-mips@vger.kernel.org, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
"open list:MEMORY CONTROLLER DRIVERS"
<linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/2] brcmstb-memc-ddr binding updates for MIPS boards
Date: Fri, 29 Aug 2025 17:36:13 +0200 [thread overview]
Message-ID: <aLHI7arPfcMDEhzM@alpha.franken.de> (raw)
In-Reply-To: <60e55e14-7712-4f82-93af-6751009327fd@kernel.org>
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 ]
next prev parent reply other threads:[~2025-08-29 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 20:52 Florian Fainelli
2025-07-29 20:52 ` [PATCH 1/2] dt-bindings: memory: Update brcmstb-memc-ddr binding with older chips Florian Fainelli
2025-07-30 22:30 ` Rob Herring (Arm)
2025-08-13 10:36 ` (subset) " Krzysztof Kozlowski
2025-07-29 20:52 ` [PATCH 2/2] MIPS: BMIPS: Properly define memory controller compatible Florian Fainelli
2025-08-29 10:21 ` [PATCH 0/2] brcmstb-memc-ddr binding updates for MIPS boards Thomas Bogendoerfer
2025-08-29 10:37 ` Krzysztof Kozlowski
2025-08-29 10:39 ` Krzysztof Kozlowski
2025-08-29 15:36 ` Thomas Bogendoerfer [this message]
2025-08-29 16:31 ` Florian Fainelli
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=aLHI7arPfcMDEhzM@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®