From: Jakub Kicinski <kuba@kernel.org>
To: Jonas Jelonek <jelonek.jonas@gmail.com>
Cc: "Oleksij Rempel" <o.rempel@pengutronix.de>,
"Kory Maincent" <kory.maincent@bootlin.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Daniel Golle" <daniel@makrotopia.org>,
"Bjørn Mork" <bjorn@mork.no>
Subject: Re: [PATCH net-next v10 1/4] dt-bindings: net: pse-pd: add bindings for Realtek PSE MCU
Date: Fri, 31 Jul 2026 17:16:39 -0700 [thread overview]
Message-ID: <20260731171639.1baec9e5@kernel.org> (raw)
In-Reply-To: <20260728084307.2129515-2-jelonek.jonas@gmail.com>
The second patch conflicts on MAINTAINERS so unfortunately a rebase
will be needed.
On Tue, 28 Jul 2026 08:43:03 +0000 Jonas Jelonek wrote:
> diff --git a/Documentation/devicetree/bindings/net/pse-pd/realtek,pse-mcu-gen1.yaml
While you rebase -- the AI points out that the binding is called
...-gen1 but it documents gen2 as well. Should the -gen1 be dropped?
next prev parent reply other threads:[~2026-08-01 0:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 8:43 [PATCH net-next v10 0/4] net: pse-pd: add Realtek PSE MCU support Jonas Jelonek
2026-07-28 8:43 ` [PATCH net-next v10 1/4] dt-bindings: net: pse-pd: add bindings for Realtek PSE MCU Jonas Jelonek
2026-07-29 9:08 ` Oleksij Rempel
2026-08-01 0:16 ` Jakub Kicinski [this message]
2026-08-01 6:51 ` Jonas Jelonek
2026-07-28 8:43 ` [PATCH net-next v10 2/4] net: pse-pd: add Realtek PSE MCU core Jonas Jelonek
2026-07-29 9:06 ` Oleksij Rempel
2026-07-28 8:43 ` [PATCH net-next v10 3/4] net: pse-pd: realtek-pse-mcu: add I2C transport Jonas Jelonek
2026-07-28 8:43 ` [PATCH net-next v10 4/4] net: pse-pd: realtek-pse-mcu: add UART transport Jonas Jelonek
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=20260731171639.1baec9e5@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bjorn@mork.no \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jelonek.jonas@gmail.com \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--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