From: patchwork-bot+netdevbpf@kernel•org
To: Tariq Toukan <tariqt@nvidia•com>
Cc: stephen@networkplumber•org, dsahern@gmail•com, jiri@resnulli•us,
edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
andrew+netdev@lunn•ch, davem@davemloft•net, saeedm@nvidia•com,
leon@kernel•org, mbloch@nvidia•com, netdev@vger•kernel.org,
linux-rdma@vger•kernel.org, linux-kernel@vger•kernel.org,
gal@nvidia•com, moshe@nvidia•com, jiri@nvidia•com,
cjubran@nvidia•com, shshitrit@nvidia•com
Subject: Re: [PATCH iproute2-next] devlink: Introduce burst period for health reporter
Date: Thu, 16 Oct 2025 15:30:21 +0000 [thread overview]
Message-ID: <176062862101.1781559.6540317333890628904.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1759906638-867747-1-git-send-email-tariqt@nvidia.com>
Hello:
This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel•org>:
On Wed, 8 Oct 2025 09:57:18 +0300 you wrote:
> From: Shahar Shitrit <shshitrit@nvidia•com>
>
> Add a new devlink health set option to configure the health
> reporter’s burst period. The burst period defines a time window
> during which recovery attempts for reported errors are allowed.
> Once this period expires, the configured grace period begins.
>
> [...]
Here is the summary with links:
- [iproute2-next] devlink: Introduce burst period for health reporter
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=56d3c9965850
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:[~2025-10-16 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 6:57 [PATCH iproute2-next] devlink: Introduce burst period for health reporter Tariq Toukan
2025-10-16 15: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=176062862101.1781559.6540317333890628904.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=cjubran@nvidia$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=gal@nvidia$(echo .)com \
--cc=jiri@nvidia$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=kuba@kernel$(echo .)org \
--cc=leon@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=mbloch@nvidia$(echo .)com \
--cc=moshe@nvidia$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=shshitrit@nvidia$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
--cc=tariqt@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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