From: patchwork-bot+netdevbpf@kernel.org
To: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, andrew@lunn.ch,
linux@rempel-privat.de, dan.j.williams@intel.com,
petrm@nvidia.com, chenhao288@hisilicon.com, amcohen@nvidia.com,
gustavoars@kernel.org, sean.anderson@seco.com,
linux-kernel@vger.kernel.org, leonro@nvidia.com
Subject: Re: [PATCH v5] ethtool: doc: clarify what drivers can implement in their get_drvinfo()
Date: Fri, 18 Nov 2022 04:50:16 +0000 [thread overview]
Message-ID: <166874701628.23195.4484319487930561442.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221116171828.4093-1-mailhol.vincent@wanadoo.fr>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 17 Nov 2022 02:18:28 +0900 you wrote:
> Many of the drivers which implement ethtool_ops::get_drvinfo() will
> prints the .driver, .version or .bus_info of struct ethtool_drvinfo.
> To have a glance of current state, do:
>
> $ git grep -W "get_drvinfo(struct"
>
> Printing in those three fields is useless because:
>
> [...]
Here is the summary with links:
- [v5] ethtool: doc: clarify what drivers can implement in their get_drvinfo()
https://git.kernel.org/netdev/net-next/c/f20a0a0519f3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-18 4:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 3:08 [PATCH] ethtool: doc: clarify what drivers can implement in their get_drvinfo() Vincent Mailhol
2022-11-11 6:40 ` [PATCH net-next v2] " Vincent Mailhol
2022-11-13 7:58 ` Leon Romanovsky
2022-11-13 8:34 ` [PATCH net-next v3] " Vincent Mailhol
2022-11-15 5:27 ` Jakub Kicinski
2022-11-15 7:52 ` Vincent MAILHOL
2022-11-15 16:28 ` Jakub Kicinski
2022-11-16 0:30 ` Vincent MAILHOL
2022-11-16 4:34 ` Vincent MAILHOL
2022-11-16 17:18 ` [PATCH v5] " Vincent Mailhol
2022-11-18 4:50 ` patchwork-bot+netdevbpf [this message]
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=166874701628.23195.4484319487930561442.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=andrew@lunn.ch \
--cc=chenhao288@hisilicon.com \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=mailhol.vincent@wanadoo.fr \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=sean.anderson@seco.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).