From: patchwork-bot+netdevbpf@kernel.org
To: Vimlesh Kumar <vimleshk@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
sedara@marvell.com, srasheed@marvell.com, hgani@marvell.com
Subject: Re: [PATCH net v4 0/3] disable interrupts and ensure dbell updation
Date: Tue, 10 Feb 2026 15:10:09 +0000 [thread overview]
Message-ID: <177073620983.3548292.5914076023087755197.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260206111510.1045092-1-vimleshk@marvell.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 6 Feb 2026 11:15:05 +0000 you wrote:
> Disable per ring interrupts when netdev goes down and ensure dbell BADDR
> updation for both PFs and VFs by adding wait and check for updated value.
>
> Resending based on discussion with reviewer.
>
> Vimlesh Kumar (3):
> octeon_ep: disable per ring interrupts
> octeon_ep: ensure dbell BADDR updation
> octeon_ep_vf: ensure dbell BADDR updation
>
> [...]
Here is the summary with links:
- [net,v4,1/3] octeon_ep: disable per ring interrupts
https://git.kernel.org/netdev/net/c/73e6ffa37ceb
- [net,v4,2/3] octeon_ep: ensure dbell BADDR updation
https://git.kernel.org/netdev/net/c/ce8fe3fc4f99
- [net,v4,3/3] octeon_ep_vf: ensure dbell BADDR updation
https://git.kernel.org/netdev/net/c/484e834d53cf
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:[~2026-02-10 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 11:15 [PATCH net v4 0/3] disable interrupts and ensure dbell updation Vimlesh Kumar
2026-02-06 11:15 ` [PATCH net v4 1/3] octeon_ep: disable per ring interrupts Vimlesh Kumar
2026-02-06 11:15 ` [PATCH net v4 2/3] octeon_ep: ensure dbell BADDR updation Vimlesh Kumar
2026-02-06 11:15 ` [PATCH net v4 3/3] octeon_ep_vf: " Vimlesh Kumar
2026-02-10 15: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=177073620983.3548292.5914076023087755197.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=hgani@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sedara@marvell.com \
--cc=srasheed@marvell.com \
--cc=vimleshk@marvell.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