netdev - Re: [PATCH net-next] gve: enhance driver name usage

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]

Date: Fri, 7 Jul 2023 16:20:22 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Junfeng Guo <junfeng.guo@...el.com>
Cc: netdev@...r.kernel.org, jeroendb@...gle.com, pkaligineedi@...gle.com,
 shailend@...gle.com, haiyue.wang@...el.com, awogbemila@...gle.com,
 davem@...emloft.net, pabeni@...hat.com, yangchun@...gle.com,
 edumazet@...gle.com
Subject: Re: [PATCH net-next] gve: enhance driver name usage

On Fri,  7 Jul 2023 10:44:05 +0800 Junfeng Guo wrote:
> Current codebase contained the usage of two different names for this
> driver (i.e., `gvnic` and `gve`), which is quite unfriendly for users
> to use, especially when trying to bind or unbind the driver manually.
> The corresponding kernel module is registered with the name of `gve`.
> It's more reasonable to align the name of the driver with the module.

Please read the guidelines before posting patches:

https://www.kernel.org/doc/html/next/process/maintainer-netdev.html