[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166621741987.14082.13421045521288464984.git-patchwork-notify@kernel.org>
Date: Wed, 19 Oct 2022 22:10:19 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: <edward.cree@....com>
Cc: netdev@...r.kernel.org, linux-net-drivers@....com,
davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
edumazet@...gle.com, habetsm.xilinx@...il.com,
johannes@...solutions.net, marcelo.leitner@...il.com,
jiri@...nulli.us, ecree.xilinx@...il.com
Subject: Re: [PATCH v3 net-next 0/3] netlink: formatted extacks
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 18 Oct 2022 15:37:26 +0100 you wrote:
> From: Edward Cree <ecree.xilinx@...il.com>
>
> Currently, netlink extacks can only carry fixed string messages, which
> is limiting when reporting failures in complex systems. This series
> adds the ability to return printf-formatted messages, and uses it in
> the sfc driver's TC offload code.
> Formatted extack messages are limited in length to a fixed buffer size,
> currently 80 characters. If the message exceeds this, the full message
> will be logged (ratelimited) to the console and a truncated version
> returned over netlink.
> There is no change to the netlink uAPI; only internal kernel changes
> are needed.
>
> [...]
Here is the summary with links:
- [v3,net-next,1/3] netlink: add support for formatted extack messages
https://git.kernel.org/netdev/net-next/c/51c352bdbcd2
- [v3,net-next,2/3] sfc: use formatted extacks instead of efx_tc_err()
https://git.kernel.org/netdev/net-next/c/ad1c80d5f777
- [v3,net-next,3/3] sfc: remove 'log-tc-errors' ethtool private flag
https://git.kernel.org/netdev/net-next/c/b799f052a987
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