From: Jakub Kicinski <kuba@kernel.org>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
netdev@vger.kernel.org, Jose Abreu <joabreu@synopsys.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Magnus Damm <magnus.damm@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH net-next v4 0/3] Add GBETH glue layer driver for Renesas RZ/V2H(P) SoC
Date: Wed, 26 Mar 2025 06:21:48 -0700 [thread overview]
Message-ID: <20250326062148.152e3daa@kernel.org> (raw)
In-Reply-To: <CA+V-a8tBh1Ev-8=0vcmz0XB7iqKzZZ5dKefrZCrY49Je3KTCAg@mail.gmail.com>
On Wed, 26 Mar 2025 12:52:17 +0000 Lad, Prabhakar wrote:
> This patch series has been marked as "Changes Requested" on Patchwork,
> but there were no review comments on the series. If the status was
> marked as "Changes Requested" due to build failures reported by the
> kernel bots, I’d like to clarify that the failure was caused by a
> patch dependency, which has now been merged into net-next [0]. As a
> result, this series should now build successfully on net-next.
>
> Please let me know if you would like me to resend the series.
Don't send patches which can't be immediately merged.
You will have to repost, obviously, and after the merge window.
next prev parent reply other threads:[~2025-03-26 13:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 20:57 [PATCH net-next v4 0/3] Add GBETH glue layer driver for Renesas RZ/V2H(P) SoC Prabhakar
2025-03-18 20:57 ` [PATCH net-next v4 1/3] dt-bindings: net: dwmac: Increase 'maxItems' for 'interrupts' and 'interrupt-names' Prabhakar
2025-03-18 20:57 ` [PATCH net-next v4 2/3] dt-bindings: net: Document support for Renesas RZ/V2H(P) GBETH Prabhakar
2025-03-18 20:57 ` [PATCH net-next v4 3/3] net: stmmac: Add DWMAC glue layer for Renesas GBETH Prabhakar
2025-03-19 18:30 ` kernel test robot
2025-03-19 18:41 ` Lad, Prabhakar
2025-03-20 0:29 ` kernel test robot
2025-03-20 10:01 ` Lad, Prabhakar
2025-03-26 12:52 ` [PATCH net-next v4 0/3] Add GBETH glue layer driver for Renesas RZ/V2H(P) SoC Lad, Prabhakar
2025-03-26 13:21 ` Jakub Kicinski [this message]
2025-03-26 13:28 ` Andrew Lunn
2025-03-26 13:34 ` Lad, Prabhakar
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=20250326062148.152e3daa@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=joabreu@synopsys.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=rmk+kernel@armlinux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.