From: patchwork-bot+netdevbpf@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, kuba@kernel.org, awogbemila@google.com,
davem@davemloft.net, pabeni@redhat.com, yangchun@google.com,
edumazet@google.com, sagis@google.com, willemb@google.com,
lrizzo@google.com, michal.kubiak@intel.com, csully@google.com
Subject: Re: [PATCH net v2] gve: unify driver name usage
Date: Mon, 10 Jul 2023 07:40:20 +0000 [thread overview]
Message-ID: <168897482032.8087.6653671878287859036.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230708031451.461738-1-junfeng.guo@intel.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Sat, 8 Jul 2023 11:14:51 +0800 you 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>
>
> [...]
Here is the summary with links:
- [net,v2] gve: unify driver name usage
https://git.kernel.org/netdev/net/c/9d0aba98316d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-07-10 7:40 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
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 [this message]
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=168897482032.8087.6653671878287859036.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@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=kuba@kernel.org \
--cc=lrizzo@google.com \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=sagis@google.com \
--cc=shailend@google.com \
--cc=willemb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.