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: <f6ae42d5-5fb8-476e-acfa-db192ac8aec9@suse.de>
Date: Thu, 15 Feb 2024 16:41:47 +0300
From: Denis Kirjanov <dkirjanov@...e.de>
To: Andrew Lunn <andrew@...n.ch>, Denis Kirjanov <kirjanov@...il.com>
Cc: mkubecek@...e.cz, netdev@...r.kernel.org
Subject: Re: [PATCH ethtool] ethtool: put driver specific code into drivers
 dir



On 2/14/24 21:12, Andrew Lunn wrote:
> 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?".

"For better code organization the patch moves the driver-specific code into drivers directory"

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

Sure, I'll put them back in the next version

> 
>     Andrew
>