The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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, devicetree@vger.kernel.org,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mips: dts: realtek: Add MDIO controller
Date: Sun, 27 Apr 2025 09:54:09 +0200	[thread overview]
Message-ID: <aA3iofwUsgBpYlTo@alpha.franken.de> (raw)
In-Reply-To: <20250415205425.1491165-1-chris.packham@alliedtelesis.co.nz>

On Wed, Apr 16, 2025 at 08:54:25AM +1200, Chris Packham wrote:
> Add a device tree node for the MDIO controller on the RTL9300 chips.
> 
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
> 
> Notes:
>     This was originally part of a series adding the bindings and the
>     driver[1]. These were split off and have now been applied via net-next.
>     That just leaves the dts changes to come in via linux-mips.
>     
>     [1] - https://lore.kernel.org/all/20250227213248.2010986-3-chris.packham@alliedtelesis.co.nz/
> 
>  arch/mips/boot/dts/realtek/rtl930x.dtsi | 33 +++++++++++++++++++++++++
>  1 file changed, 33 insertions(+)

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 ]

      reply	other threads:[~2025-04-27  8:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 20:54 [PATCH] mips: dts: realtek: Add MDIO controller Chris Packham
2025-04-27  7:54 ` 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=aA3iofwUsgBpYlTo@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=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