netdev - [RFC PATCH 0/2] Add concept of rolling start/stop to phylink

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

Message-ID: 
 <174493388712.1021855.5688275689821876896.stgit@ahduyck-xeon-server.home.arpa>
Date: Thu, 17 Apr 2025 16:56:19 -0700
From: Alexander Duyck <alexander.duyck@...il.com>
To: linux@...linux.org.uk
Cc: netdev@...r.kernel.org, andrew@...n.ch, kuba@...nel.org
Subject: [RFC PATCH 0/2] Add concept of rolling start/stop to phylink

This is based on the conversations I was having with Russell earlier. I am
mostly just looking for feedback on if this is a viable approach for this
or not.

As it stands I will need to wait for the patches submitted to net to get
synced back up to net-next so I will likely be waiting several days for
that. The main thing I am looking for is if this is acceptable so I can go
back to working on the rest of the driver.

---

Alexander Duyck (2):
      net: phylink: Add support for link initialization w/ a "rolling start"
      net: phylink: Extend phylink_suspend to support a "rolling stop"

 drivers/net/ethernet/meta/fbnic/fbnic_netdev.c  |  5 -----
 drivers/net/ethernet/meta/fbnic/fbnic_phylink.c |  1 +
 drivers/net/phy/phylink.c                       | 17 ++++++++++++-----
 include/linux/phylink.h                         |  4 ++++
 4 files changed, 17 insertions(+), 10 deletions(-)

--