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: <c3bd51cc-fc8f-46b5-bfc3-ccb0fa1386e9@lunn.ch>
Date: Sun, 15 Sep 2024 22:21:16 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Hans-Frieder Vogt <hfdevel@....net>
Cc: netdev@...r.kernel.org, Heiner Kallweit <hkallweit1@...il.com>,
	Russell King <linux@...linux.org.uk>,
	FUJITA Tomonori <fujita.tomonori@...il.com>,
	"David S. Miller" <davem@...emloft.net>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	Eric Dumazet <edumazet@...gle.com>,
	Vladimir Oltean <vladimir.oltean@....com>
Subject: Re: [PATCH net-next v2 0/7] net: tn40xx: add support for AQR105
 based cards

On Sun, Sep 15, 2024 at 09:48:17PM +0200, Hans-Frieder Vogt wrote:
> This patch series adds support to the Tehuti tn40xx driver for TN9510 cards
> which combine a TN4010 MAC with an Aquantia AQR105.
> It is an update of the patch series "net: tn40xx: add support for AQR105 based cards",
> https://lore.kernel.org/netdev/trinity-33332a4a-1c44-46b7-8526-b53b1a94ffc2-1726082106356@3c-app-gmx-bs04/
> addressing review comments and generally cleaning up the series.

Hi Hans-Frieder

A few process issues first, before i get to the patches themselves.

We are currently in the merged window, so net-next is closed.

https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html

You can send patches, but please mark them as RFC.

You have one patch with the wrong subject, not net-next, but net-dev.

Your emails are not threaded together.

These last two point suggest you are not using the tools correctly.
You should have all the code on one branch, then use

git format-patch --cover-letter --subject-prefix="RFC PATCH v2 net-next" HEAD~42

and then use git send-email to actually send the patches. That will
cause them to be threaded together.

Alternatively look at b4 prep:

https://b4.docs.kernel.org/en/latest/contributor/prep.html

It handles a lot of the details for you.

	Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ