[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166874701628.23195.4484319487930561442.git-patchwork-notify@kernel.org>
Date: Fri, 18 Nov 2022 04:50:16 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Vincent Mailhol <mailhol.vincent@...adoo.fr>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, netdev@...r.kernel.org, andrew@...n.ch,
linux@...pel-privat.de, dan.j.williams@...el.com, petrm@...dia.com,
chenhao288@...ilicon.com, amcohen@...dia.com,
gustavoars@...nel.org, sean.anderson@...o.com,
linux-kernel@...r.kernel.org, leonro@...dia.com
Subject: Re: [PATCH v5] ethtool: doc: clarify what drivers can implement in their
get_drvinfo()
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@...nel.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
Powered by blists - more mailing lists