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: <657cf1e4-a27a-4d9d-9931-494ce26ef325@lunn.ch>
Date: Mon, 20 Oct 2025 21:01:13 +0200
From: Andrew Lunn <andrew@...n.ch>
To: zuoqian <zuoqian113@...il.com>
Cc: nicolas.ferre@...rochip.com, claudiu.beznea@...on.dev,
	andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
	kuba@...nel.org, pabeni@...hat.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] net: macb: enable IPv6 support for TSO

On Mon, Oct 20, 2025 at 09:55:08AM +0000, zuoqian wrote:
> New Cadence GEM hardware support TSO for both ipv4 and IPv6 protocols,

What about the 'Old' Cadence GEM hardware? I'm assuming you mean
something by New here. So it would be good to make a comment something
like that IPv4 and IPv6 TSO was added at the same time. So if IPv4 TSO
is supported, IPv6 TSO should also be supported, so there is no danger
of regressions with older GEM hardware.

> Signed-off-by: zuoqian <zuoqian113@...il.com>

This means you are agreeing to:

https://docs.kernel.org/process/submitting-patches.html#developer-s-certificate-of-origin-1-1

However, we say "using a known identity", since this is a legal
statement. I don't think zuoqian qualifies. Please you a full name
here.

    Andrew

---
pw-bot: cr

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ