From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
jiri@resnulli.us, petrm@nvidia.com, jianbol@nvidia.com,
roid@nvidia.com, vladbu@nvidia.com, olteanv@gmail.com,
simon.horman@corigine.com, baowen.zheng@corigine.com,
marcelo.leitner@gmail.com
Subject: Re: [PATCH net-next 00/14] net/sched: Better error reporting for offload failures
Date: Fri, 08 Apr 2022 12:50:16 +0000 [thread overview]
Message-ID: <164942221682.10804.2065514338670048792.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220407073533.2422896-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 7 Apr 2022 10:35:19 +0300 you wrote:
> This patchset improves error reporting to user space when offload fails
> during the flow action setup phase. That is, when failures occur in the
> actions themselves, even before calling device drivers. Requested /
> reported in [1].
>
> This is done by passing extack to the offload_act_setup() callback and
> making use of it in the various actions.
>
> [...]
Here is the summary with links:
- [net-next,01/14] net/sched: matchall: Take verbose flag into account when logging error messages
https://git.kernel.org/netdev/net-next/c/4c096ea2d67c
- [net-next,02/14] net/sched: flower: Take verbose flag into account when logging error messages
https://git.kernel.org/netdev/net-next/c/11c95317bc1a
- [net-next,03/14] net/sched: act_api: Add extack to offload_act_setup() callback
https://git.kernel.org/netdev/net-next/c/c2ccf84ecb71
- [net-next,04/14] net/sched: act_gact: Add extack messages for offload failure
https://git.kernel.org/netdev/net-next/c/69642c2ab2f5
- [net-next,05/14] net/sched: act_mirred: Add extack message for offload failure
https://git.kernel.org/netdev/net-next/c/4dcaa50d0292
- [net-next,06/14] net/sched: act_mpls: Add extack messages for offload failure
https://git.kernel.org/netdev/net-next/c/bca3821d19d9
- [net-next,07/14] net/sched: act_pedit: Add extack message for offload failure
https://git.kernel.org/netdev/net-next/c/bf3b99e4f9ce
- [net-next,08/14] net/sched: act_police: Add extack messages for offload failure
https://git.kernel.org/netdev/net-next/c/b50e462bc22d
- [net-next,09/14] net/sched: act_skbedit: Add extack messages for offload failure
https://git.kernel.org/netdev/net-next/c/a9c64939b669
- [net-next,10/14] net/sched: act_tunnel_key: Add extack message for offload failure
https://git.kernel.org/netdev/net-next/c/ee367d44b936
- [net-next,11/14] net/sched: act_vlan: Add extack message for offload failure
https://git.kernel.org/netdev/net-next/c/f8fab3169464
- [net-next,12/14] net/sched: cls_api: Add extack message for unsupported action offload
https://git.kernel.org/netdev/net-next/c/c440615ffbcb
- [net-next,13/14] net/sched: matchall: Avoid overwriting error messages
https://git.kernel.org/netdev/net-next/c/0cba5c34b8f4
- [net-next,14/14] net/sched: flower: Avoid overwriting error messages
https://git.kernel.org/netdev/net-next/c/fd23e0e250c6
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:[~2022-04-08 12:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 7:35 [PATCH net-next 00/14] net/sched: Better error reporting for offload failures Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 01/14] net/sched: matchall: Take verbose flag into account when logging error messages Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 02/14] net/sched: flower: " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 03/14] net/sched: act_api: Add extack to offload_act_setup() callback Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 04/14] net/sched: act_gact: Add extack messages for offload failure Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 05/14] net/sched: act_mirred: Add extack message " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 06/14] net/sched: act_mpls: Add extack messages " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 07/14] net/sched: act_pedit: Add extack message " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 08/14] net/sched: act_police: Add extack messages " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 09/14] net/sched: act_skbedit: " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 10/14] net/sched: act_tunnel_key: Add extack message " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 11/14] net/sched: act_vlan: " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 12/14] net/sched: cls_api: Add extack message for unsupported action offload Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 13/14] net/sched: matchall: Avoid overwriting error messages Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 14/14] net/sched: flower: " Ido Schimmel
2022-04-07 21:15 ` [PATCH net-next 00/14] net/sched: Better error reporting for offload failures Jamal Hadi Salim
2022-04-08 12:50 ` patchwork-bot+netdevbpf [this message]
2022-04-08 18:51 ` Marcelo Ricardo Leitner
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=164942221682.10804.2065514338670048792.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=baowen.zheng@corigine.com \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jhs@mojatatu.com \
--cc=jianbol@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=roid@nvidia.com \
--cc=simon.horman@corigine.com \
--cc=vladbu@nvidia.com \
--cc=xiyou.wangcong@gmail.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