netdev - [PATCH 00/15] net: ftgmac100: Various probe cleanups

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] [day] [month] [year] [list]

Message-ID:
 <SEYPR06MB513424718263D12DE440451B9D85A@SEYPR06MB5134.apcprd06.prod.outlook.com>
Date: Thu, 8 Jan 2026 01:37:47 +0000
From: Jacky Chou <jacky_chou@...eedtech.com>
To: Simon Horman <horms@...nel.org>
CC: Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"
	<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski
	<kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, "netdev@...r.kernel.org"
	<netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, Andrew Lunn <andrew@...n.ch>
Subject: [PATCH 00/15] net: ftgmac100: Various probe cleanups

> I'm slightly unclear on the providence of this patchset.
> But overall it looks good to me. And I particularly like how it has been split up
> into bite-sized chunks.
> 
> I don't see anything that should block progress, but I do have a few minor nits
> that I'll raise just in case there is a v2 for other reasons.
> 
> The first nit is that the patch-set should be targeted at net-next, by including
> inet-next in the Subjects, like this:
> 
>   [PATCH net-net 00/15] ...
> 
> The other minor nits are patch-specifically, so I'll respond to those patches
> accordingly.
> 
> Again, overall this looks good to me.
> So for the series:
> 
> Reviewed-by: Simon Horman <horms@...nel.org>

Hi Simon,

Thank you very much for the careful review and the positive feedback.

We really appreciate Andrew's help in organizing and shaping this patch series - 
his guidance was invaluable in getting it into its current form.
We'll incorporate your suggestion regarding targeting net-next (including the
net-next tag in the subject) and will make the appropriate adjustments in the
next revision of the series.

Thanks again for your time and for the detailed review.

Best regards,
Jacky