netdev - Re: [PATCH] usbnet: Set duplex status to unknown in the absence of MII

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: <20250723152151.70a8034b@kernel.org>
Date: Wed, 23 Jul 2025 15:21:51 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: yicongsrfy@....com, andrew+netdev@...n.ch, davem@...emloft.net,
 linux-usb@...r.kernel.org, netdev@...r.kernel.org, oneukum@...e.com,
 yicong@...inos.cn
Subject: Re: [PATCH] usbnet: Set duplex status to unknown in the absence of
 MII

On Wed, 23 Jul 2025 15:05:27 +0200 Andrew Lunn wrote:
> > > Thanks for checking this.
> > >
> > > Just one more question. This is kind of flipping the question on its
> > > head. Does the standard say devices are actually allowed to support
> > > 1/2 duplex? Does it say they are not allowed to support 1/2 duplex?
> > >
> > > If duplex is not reported, maybe it is because 1/2 duplex is simply
> > > not allowed, so there is no need to report it.
> > >  
> > 
> > No, the standard does not mention anything about duplex at all.  
> 
> O.K. So please set duplex to unknown.

.. and update the commit message and the code comment to reflect 
the outcome of the discussion better.
-- 
pw-bot: cr