From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Ezra Buehler <ezra@easyb.ch>
Cc: linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
Conor Dooley <conor+dt@kernel.org>,
Harvey Hunt <harveyhuntnexus@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Reto Schneider <reto.schneider@husqvarnagroup.com>,
Rob Herring <robh@kernel.org>,
Sergio Paracuellos <sergio.paracuellos@gmail.com>,
Stefan Roese <sr@denx.de>,
Ezra Buehler <ezra.buehler@husqvarnagroup.com>
Subject: Re: [PATCH v4 0/4] MIPS: dts: ralink: mt7628a: Tweak for GARDENA smart Gateway
Date: Wed, 2 Jul 2025 14:03:02 +0200 [thread overview]
Message-ID: <aGUf9sLDQgJHGy3M@alpha.franken.de> (raw)
In-Reply-To: <20250624115810.37851-1-ezra@easyb.ch>
On Tue, Jun 24, 2025 at 01:58:06PM +0200, Ezra Buehler wrote:
> From: Ezra Buehler <ezra.buehler@husqvarnagroup.com>
>
> Various devicetree changes needed for the MT7688-based GARDENA smart
> Gateway.
>
> Signed-off-by: Ezra Buehler <ezra.buehler@husqvarnagroup.com>
> ---
> Changes in v4:
> - Re-add ralink,mt7688-sysc to enum in mediatek,mtmips-sysc DT binding
> - Link to v3: https://lore.kernel.org/20250619203502.1293695-1-ezra@easyb.ch
>
> Changes in v3:
> - Remove duplicate entries in mediatek,mtmips-sysc DT binding
> - Link to v2: https://lore.kernel.org/20250617103058.1125836-1-ezra@easyb.ch
>
> Changes in v2:
> - Add patch for mediatek,mtmips-sysc DT binding
> - Add Reviewed-by tags
> - Link to v1: https://lore.kernel.org/20250611194716.302126-1-ezra@easyb.ch
>
> Ezra Buehler (4):
> dt-bindings: clock: mediatek,mtmips-sysc: Adapt compatible for MT7688
> boards
> MIPS: dts: ralink: mt7628a: Fix sysc's compatible property for MT7688
> MIPS: dts: ralink: mt7628a: Update watchdog node according to bindings
> MIPS: dts: ralink: gardena_smart_gateway_mt7688: Fix power LED
>
> .../bindings/clock/mediatek,mtmips-sysc.yaml | 28 +++++++++++--------
> .../ralink/gardena_smart_gateway_mt7688.dts | 2 +-
> arch/mips/boot/dts/ralink/mt7628a.dtsi | 11 ++------
> 3 files changed, 20 insertions(+), 21 deletions(-)
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2025-07-02 13:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 11:58 [PATCH v4 0/4] MIPS: dts: ralink: mt7628a: Tweak for GARDENA smart Gateway Ezra Buehler
2025-06-24 11:58 ` [PATCH v4 1/4] dt-bindings: clock: mediatek,mtmips-sysc: Adapt compatible for MT7688 boards Ezra Buehler
2025-06-25 7:13 ` Krzysztof Kozlowski
2025-06-25 8:21 ` Sergio Paracuellos
2025-06-24 11:58 ` [PATCH v4 2/4] MIPS: dts: ralink: mt7628a: Fix sysc's compatible property for MT7688 Ezra Buehler
2025-06-25 8:21 ` Sergio Paracuellos
2025-06-24 11:58 ` [PATCH v4 3/4] MIPS: dts: ralink: mt7628a: Update watchdog node according to bindings Ezra Buehler
2025-06-24 11:58 ` [PATCH v4 4/4] MIPS: dts: ralink: gardena_smart_gateway_mt7688: Fix power LED Ezra Buehler
2025-07-02 12:03 ` Thomas Bogendoerfer [this message]
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=aGUf9sLDQgJHGy3M@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ezra.buehler@husqvarnagroup.com \
--cc=ezra@easyb.ch \
--cc=harveyhuntnexus@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=reto.schneider@husqvarnagroup.com \
--cc=robh@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=sr@denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.