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: <6e729b11-74de-4f9d-8aa4-ecac0edb7681@linux.alibaba.com>
Date: Mon, 22 Dec 2025 20:44:29 +0800
From: Wen Gu <guwen@...ux.alibaba.com>
To: David Woodhouse <dwmw2@...radead.org>, Jakub Kicinski <kuba@...nel.org>,
 Thomas Weißschuh <thomas.weissschuh@...utronix.de>,
 Thomas Gleixner <tglx@...utronix.de>
Cc: richardcochran@...il.com, andrew+netdev@...n.ch, davem@...emloft.net,
 edumazet@...gle.com, pabeni@...hat.com, xuanzhuo@...ux.alibaba.com,
 dust.li@...ux.alibaba.com, netdev@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v5 1/2] ptp: introduce Alibaba CIPU PHC driver



On 2025/12/18 20:28, David Woodhouse wrote:

> 
> Having said that, it does seem rather harsh to refuse to accept this
> one when there are so many other examples already in the tree. I'd
> suggest that we accept it and then it can be moved to the new setup,
> whatever that is, along with the other legacy snapshot-only PHCs.
> 

That's also my thought.

That said, I'm open to either: accept it and re-home these similar
drivers when we have a better setup, or agree on a dedicated "pure
PHC" subsystem now and then merge it there.

Regards.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ