netdev - Re: [PATCH ethtool] ethtool: put driver specific code into drivers dir

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: <2951e395-7982-47bb-a9f6-c732c2affaaf@lunn.ch>
Date: Wed, 14 Feb 2024 19:12:15 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Denis Kirjanov <kirjanov@...il.com>
Cc: mkubecek@...e.cz, netdev@...r.kernel.org,
	Denis Kirjanov <dkirjanov@...e.de>
Subject: Re: [PATCH ethtool] ethtool: put driver specific code into drivers
 dir

On Wed, Feb 14, 2024 at 08:55:05AM -0500, Denis Kirjanov wrote:
> the patch moves the driver specific code in drivers
> directory

It is normal for the commit message to give the answer to the question
"Why?".

Also, what is your definition of a driver? I would not really call the
sfp parts drivers.

    Andrew