[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21bebfcd-8289-4512-a8d4-3fda56cf3a6a@lunn.ch>
Date: Sat, 8 Jul 2023 23:20:15 +0200
From: Andrew Lunn <andrew@...n.ch>
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, kuba@...nel.org,
awogbemila@...gle.com, davem@...emloft.net, pabeni@...hat.com,
yangchun@...gle.com, edumazet@...gle.com, sagis@...gle.com,
willemb@...gle.com, lrizzo@...gle.com, michal.kubiak@...el.com,
csully@...gle.com
Subject: Re: [PATCH net v2] gve: unify driver name usage
On Sat, Jul 08, 2023 at 11:14:51AM +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.
>
> Fixes: 893ce44df565 ("gve: Add basic driver framework for Compute Engine Virtual NIC")
You are posting this for net, and have a fixes tag. Please take a look at:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
Do you think it fulfils those rules?
Andrew
Powered by blists - more mailing lists