lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d614f117-d07d-4ac8-b5e7-7114a3ec8404@lunn.ch>
Date: Wed, 26 Mar 2025 14:28:49 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Jakub Kicinski <kuba@...nel.org>
Cc: "Lad, Prabhakar" <prabhakar.csengg@...il.com>,
	Paolo Abeni <pabeni@...hat.com>,
	Philipp Zabel <p.zabel@...gutronix.de>,
	Conor Dooley <conor+dt@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Rob Herring <robh@...nel.org>, netdev@...r.kernel.org,
	Jose Abreu <joabreu@...opsys.com>,
	Giuseppe Cavallaro <peppe.cavallaro@...com>,
	"Russell King (Oracle)" <rmk+kernel@...linux.org.uk>,
	Magnus Damm <magnus.damm@...il.com>,
	Geert Uytterhoeven <geert+renesas@...der.be>,
	Eric Dumazet <edumazet@...gle.com>,
	"David S. Miller" <davem@...emloft.net>,
	Andrew Lunn <andrew+netdev@...n.ch>, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
	Biju Das <biju.das.jz@...renesas.com>,
	Fabrizio Castro <fabrizio.castro.jz@...esas.com>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
Subject: Re: [PATCH net-next v4 0/3] Add GBETH glue layer driver for Renesas
 RZ/V2H(P) SoC

On Wed, Mar 26, 2025 at 06:21:48AM -0700, Jakub Kicinski wrote:
> 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.

Just expanding on that a bit. We do more than build testing of
patches. Some runtime testing is also performed. So if they failed to
build, they cannot be fully tested. Hence the request to only post
patches which build.

You can however send the patches as RFC, so we know to ignore them for
merging.

	Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ