From: Jakub Kicinski <kuba@kernel.org>
To: Junfeng Guo <junfeng.guo@intel.com>
Cc: netdev@vger.kernel.org, jeroendb@google.com,
pkaligineedi@google.com, shailend@google.com,
haiyue.wang@intel.com, awogbemila@google.com,
davem@davemloft.net, pabeni@redhat.com, yangchun@google.com,
edumazet@google.com, csully@google.com
Subject: Re: [PATCH net] gve: unify driver name usage
Date: Fri, 7 Jul 2023 15:20:24 -0700 [thread overview]
Message-ID: <20230707152024.0807c5ba@kernel.org> (raw)
In-Reply-To: <20230707103710.3946651-1-junfeng.guo@intel.com>
On Fri, 7 Jul 2023 18:37:10 +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")
> Cc: csully@google.com
> Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
Google's maintainers definitely need to agree to this, because it's
a user visible change. It can very well break someone's scripts.
> diff --git a/drivers/net/ethernet/google/gve/gve.h b/drivers/net/ethernet/google/gve/gve.h
> index 98eb78d98e9f..4b425bf71ede 100644
> --- a/drivers/net/ethernet/google/gve/gve.h
> +++ b/drivers/net/ethernet/google/gve/gve.h
> @@ -964,5 +964,6 @@ void gve_handle_report_stats(struct gve_priv *priv);
> /* exported by ethtool.c */
> extern const struct ethtool_ops gve_ethtool_ops;
> /* needed by ethtool */
> +extern char gve_driver_name[];
> extern const char gve_version_str[];
> #endif /* _GVE_H_ */
> diff --git a/drivers/net/ethernet/google/gve/gve_adminq.c b/drivers/net/ethernet/google/gve/gve_adminq.c
> index 252974202a3f..ae8f8c935bbe 100644
> --- a/drivers/net/ethernet/google/gve/gve_adminq.c
> +++ b/drivers/net/ethernet/google/gve/gve_adminq.c
> @@ -899,7 +899,7 @@ int gve_adminq_verify_driver_compatibility(struct gve_priv *priv,
>
> int gve_adminq_report_link_speed(struct gve_priv *priv)
> {
> - union gve_adminq_command gvnic_cmd;
> + union gve_adminq_command gve_cmd;
> dma_addr_t link_speed_region_bus;
> __be64 *link_speed_region;
> int err;
> @@ -911,12 +911,12 @@ int gve_adminq_report_link_speed(struct gve_priv *priv)
> if (!link_speed_region)
> return -ENOMEM;
>
> - memset(&gvnic_cmd, 0, sizeof(gvnic_cmd));
> - gvnic_cmd.opcode = cpu_to_be32(GVE_ADMINQ_REPORT_LINK_SPEED);
> - gvnic_cmd.report_link_speed.link_speed_address =
> + memset(&gve_cmd, 0, sizeof(gve_cmd));
> + gve_cmd.opcode = cpu_to_be32(GVE_ADMINQ_REPORT_LINK_SPEED);
> + gve_cmd.report_link_speed.link_speed_address =
> cpu_to_be64(link_speed_region_bus);
>
> - err = gve_adminq_execute_cmd(priv, &gvnic_cmd);
> + err = gve_adminq_execute_cmd(priv, &gve_cmd);
What's the problem with the variable being called gvnic_cmd ?
Please limit renames, if you want this to be a fix.
--
pw-bot: cr
next prev parent reply other threads:[~2023-07-07 22:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 10:37 [PATCH net] gve: unify driver name usage Junfeng Guo
2023-07-07 18:26 ` Michal Kubiak
2023-07-08 2:50 ` Guo, Junfeng
2023-07-07 22:20 ` Jakub Kicinski [this message]
2023-07-08 2:58 ` Guo, Junfeng
2023-07-08 3:14 ` [PATCH net v2] " Junfeng Guo
2023-07-08 21:20 ` Andrew Lunn
2023-07-10 7:40 ` patchwork-bot+netdevbpf
2023-07-11 13:13 ` [PATCH net] " Alexander Lobakin
2023-07-11 17:24 ` Wang, Haiyue
2023-07-12 16:55 ` Alexander Lobakin
2023-07-12 17:44 ` Wang, Haiyue
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230707152024.0807c5ba@kernel.org \
--to=kuba@kernel.org \
--cc=awogbemila@google.com \
--cc=csully@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haiyue.wang@intel.com \
--cc=jeroendb@google.com \
--cc=junfeng.guo@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=shailend@google.com \
--cc=yangchun@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).