From: Jakub Kicinski <kuba@kernel.org>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: Sergey Shtylyov <s.shtylyov@omp.ru>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [net-next,v4 0/2] ravb: Support describing the MDIO bus
Date: Thu, 28 Mar 2024 08:28:01 -0700 [thread overview]
Message-ID: <20240328082801.6ec0d406@kernel.org> (raw)
In-Reply-To: <20240328094546.GI1108818@ragnatech.se>
On Thu, 28 Mar 2024 10:45:46 +0100 Niklas Söderlund wrote:
> This series was marked as Deferred in patchwork. I just wonder why that
> is? Patch 1/2 touches bindings so it could go thru the Renesas tree but
> patch 2/2 touches the driver and depends on 1/2. Should not this whole
> series go thru net-next?
I don't see why either. Looks ready to apply, TBH.
pw-bot: under-review
I'll get to applying later today, hopefully.
next prev parent reply other threads:[~2024-03-28 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 15:34 [net-next,v4 0/2] ravb: Support describing the MDIO bus Niklas Söderlund
2024-03-25 15:34 ` [net-next,v4 1/2] dt-bindings: net: renesas,etheravb: Add optional MDIO bus node Niklas Söderlund
2024-03-25 15:34 ` [net-next,v4 2/2] ravb: Add support for an optional MDIO mode Niklas Söderlund
2024-03-28 9:45 ` [net-next,v4 0/2] ravb: Support describing the MDIO bus Niklas Söderlund
2024-03-28 15:28 ` Jakub Kicinski [this message]
2024-03-29 1:30 ` patchwork-bot+netdevbpf
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=20240328082801.6ec0d406@kernel.org \
--to=kuba@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=s.shtylyov@omp.ru \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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).