From: patchwork-bot+netdevbpf@kernel.org
To: <edward.cree@amd.com>
Cc: netdev@vger.kernel.org, linux-net-drivers@amd.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, habetsm.xilinx@gmail.com,
johannes@sipsolutions.net, marcelo.leitner@gmail.com,
jiri@resnulli.us, ecree.xilinx@gmail.com
Subject: Re: [PATCH v3 net-next 0/3] netlink: formatted extacks
Date: Wed, 19 Oct 2022 22:10:19 +0000 [thread overview]
Message-ID: <166621741987.14082.13421045521288464984.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1666102698.git.ecree.xilinx@gmail.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 18 Oct 2022 15:37:26 +0100 you wrote:
> From: Edward Cree <ecree.xilinx@gmail.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
prev parent reply other threads:[~2022-10-19 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 14:37 [PATCH v3 net-next 0/3] netlink: formatted extacks edward.cree
2022-10-18 14:37 ` [PATCH v3 net-next 1/3] netlink: add support for formatted extack messages edward.cree
2022-10-19 2:09 ` Jakub Kicinski
2022-10-19 20:05 ` Jakub Kicinski
2022-10-18 14:37 ` [PATCH v3 net-next 2/3] sfc: use formatted extacks instead of efx_tc_err() edward.cree
2022-10-18 14:37 ` [PATCH v3 net-next 3/3] sfc: remove 'log-tc-errors' ethtool private flag edward.cree
2022-10-19 22:10 ` 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=166621741987.14082.13421045521288464984.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=habetsm.xilinx@gmail.com \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.