From: Jakub Kicinski <kuba@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
lee@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com,
tsbogend@alpha.franken.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-mips@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next 0/5] dt-bindings: net: realtek,rtl9301-switch
Date: Tue, 18 Feb 2025 06:55:45 -0800 [thread overview]
Message-ID: <20250218065545.533bab5f@kernel.org> (raw)
In-Reply-To: <20250214134528.4630b6b2@kernel.org>
On Fri, 14 Feb 2025 13:45:28 -0800 Jakub Kicinski wrote:
> On Mon, 10 Feb 2025 12:47:46 +1300 Chris Packham wrote:
> > dt-bindings: net: Move realtek,rtl9301-switch to net
> > dt-bindings: net: Add switch ports and interrupts to RTL9300
> > dt-bindings: net: Add Realtek MDIO controller
>
> AFAIU we're waiting for a review from DT maintainers on this one,
> is this series on your radar?
Not sure why we're getting no reviews here.
Chris, could you repost? Maybe we'll get this back into people's review
queues that way..
--
pw-bot: defer
next prev parent reply other threads:[~2025-02-18 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 23:47 [PATCH net-next 0/5] dt-bindings: net: realtek,rtl9301-switch Chris Packham
2025-02-09 23:47 ` [PATCH net-next 1/5] dt-bindings: net: Move realtek,rtl9301-switch to net Chris Packham
2025-02-09 23:47 ` [PATCH net-next 2/5] dt-bindings: net: Add switch ports and interrupts to RTL9300 Chris Packham
2025-02-09 23:47 ` [PATCH net-next 3/5] dt-bindings: net: Add Realtek MDIO controller Chris Packham
2025-02-09 23:47 ` [PATCH net-next 4/5] mips: dts: realtek: Add switch interrupts Chris Packham
2025-02-09 23:47 ` [PATCH net-next 5/5] mips: dts: cameo-rtl9302c: Add switch block Chris Packham
2025-02-14 21:45 ` [PATCH net-next 0/5] dt-bindings: net: realtek,rtl9301-switch Jakub Kicinski
2025-02-18 14:55 ` Jakub Kicinski [this message]
2025-02-18 19:43 ` Chris Packham
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=20250218065545.533bab5f@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=tsbogend@alpha.franken.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 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).