From: patchwork-bot+netdevbpf@kernel.org
To: Moshe Shemesh <moshe@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, jiri@nvidia.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 00/10] devlink: cleanups and move devlink health functionality to separate file
Date: Thu, 16 Feb 2023 03:30:21 +0000 [thread overview]
Message-ID: <167651822192.29240.16746598808039292318.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1676392686-405892-1-git-send-email-moshe@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 14 Feb 2023 18:37:56 +0200 you wrote:
> This patchset moves devlink health callbacks, helpers and related code
> from leftover.c to new file health.c. About 1.3K LoC are moved by this
> patchset, covering all devlink health functionality.
>
> In addition this patchset includes a couple of small cleanups in devlink
> health code and documentation update.
>
> [...]
Here is the summary with links:
- [net-next,v2,01/10] devlink: Split out health reporter create code
https://git.kernel.org/netdev/net-next/c/b4740e3a8137
- [net-next,v2,02/10] devlink: health: Fix nla_nest_end in error flow
https://git.kernel.org/netdev/net-next/c/bfd4e6a5dbbc
- [net-next,v2,03/10] devlink: Move devlink health get and set code to health file
https://git.kernel.org/netdev/net-next/c/db6b5f3ec400
- [net-next,v2,04/10] devlink: Move devlink health report and recover to health file
https://git.kernel.org/netdev/net-next/c/55b9b2496852
- [net-next,v2,05/10] devlink: Move devlink fmsg and health diagnose to health file
https://git.kernel.org/netdev/net-next/c/a929df7fd9c6
- [net-next,v2,06/10] devlink: Move devlink health dump to health file
https://git.kernel.org/netdev/net-next/c/7004c6c45761
- [net-next,v2,07/10] devlink: Move devlink health test to health file
https://git.kernel.org/netdev/net-next/c/c9311ee13f0e
- [net-next,v2,08/10] devlink: Move health common function to health file
https://git.kernel.org/netdev/net-next/c/12af29e7790a
- [net-next,v2,09/10] devlink: Update devlink health documentation
https://git.kernel.org/netdev/net-next/c/c745cfb27ae3
- [net-next,v2,10/10] devlink: Fix TP_STRUCT_entry in trace of devlink health report
https://git.kernel.org/netdev/net-next/c/d0ab772c1f15
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:[~2023-02-16 3:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 16:37 [PATCH net-next v2 00/10] devlink: cleanups and move devlink health functionality to separate file Moshe Shemesh
2023-02-14 16:37 ` [PATCH net-next v2 01/10] devlink: Split out health reporter create code Moshe Shemesh
2023-02-15 7:52 ` Jiri Pirko
2023-02-14 16:37 ` [PATCH net-next v2 02/10] devlink: health: Fix nla_nest_end in error flow Moshe Shemesh
2023-02-14 16:37 ` [PATCH net-next v2 03/10] devlink: Move devlink health get and set code to health file Moshe Shemesh
2023-02-14 16:38 ` [PATCH net-next v2 04/10] devlink: Move devlink health report and recover " Moshe Shemesh
2023-02-14 16:38 ` [PATCH net-next v2 05/10] devlink: Move devlink fmsg and health diagnose " Moshe Shemesh
2023-02-14 16:38 ` [PATCH net-next v2 06/10] devlink: Move devlink health dump " Moshe Shemesh
2023-02-14 16:38 ` [PATCH net-next v2 07/10] devlink: Move devlink health test " Moshe Shemesh
2023-02-14 16:38 ` [PATCH net-next v2 08/10] devlink: Move health common function " Moshe Shemesh
2023-02-14 16:38 ` [PATCH net-next v2 09/10] devlink: Update devlink health documentation Moshe Shemesh
2023-02-14 16:38 ` [PATCH net-next v2 10/10] devlink: Fix TP_STRUCT_entry in trace of devlink health report Moshe Shemesh
2023-02-15 7:52 ` Jiri Pirko
2023-02-16 3:30 ` 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=167651822192.29240.16746598808039292318.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
/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.