From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
sander@svanheule.net, markus.stockhausen@gmx.de,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] mips: dts: Updates for RTL9300
Date: Wed, 2 Jul 2025 14:02:30 +0200 [thread overview]
Message-ID: <aGUf1rLBbcuKCHTC@alpha.franken.de> (raw)
In-Reply-To: <20250619010754.3760612-1-chris.packham@alliedtelesis.co.nz>
On Thu, Jun 19, 2025 at 01:07:50PM +1200, Chris Packham wrote:
> This is a series of small dts changes for the RTL9300 to enable various
> peripherals.
>
> Chris Packham (4):
> mips: dts: cameo-rtl9302c: Add switch block
> mips: dts: realtek: Add switch interrupts
> mips: dts: realtek: Add watchdog
> mips: dts: realtek: Add gpio block
>
> .../cameo-rtl9302c-2x-rtl8224-2xge.dts | 96 +++++++++++++++++++
> arch/mips/boot/dts/realtek/rtl930x.dtsi | 31 ++++++
> 2 files changed, 127 insertions(+)
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: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 1:07 [PATCH 0/4] mips: dts: Updates for RTL9300 Chris Packham
2025-06-19 1:07 ` [PATCH 1/4] mips: dts: cameo-rtl9302c: Add switch block Chris Packham
2025-06-19 1:07 ` [PATCH 2/4] mips: dts: realtek: Add switch interrupts Chris Packham
2025-06-19 1:07 ` [PATCH 3/4] mips: dts: realtek: Add watchdog Chris Packham
2025-06-19 1:07 ` [PATCH 4/4] mips: dts: realtek: Add gpio block Chris Packham
2025-07-02 12:02 ` 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=aGUf1rLBbcuKCHTC@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=markus.stockhausen@gmx.de \
--cc=robh@kernel.org \
--cc=sander@svanheule.net \
/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;
as well as URLs for NNTP newsgroup(s).