From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
kernel-team@meta.com, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [next-next PATCH v2 0/2] eth: fbnic: Update BMC MAC address handling
Date: Fri, 02 Oct 2026 01:20:10 +0000 [thread overview]
Message-ID: <179090401002.3168550.17513563940881597735.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <179061185153.414394.13396934246780284806.stgit@ahduyck-xeon-server.home.arpa>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 28 Sep 2026 09:12:00 -0700 you wrote:
> Update the handling of BMC MAC addresses on fbnic, and in the process also
> address several issues identified with the changes. This patch series
> consists of 2 patches.
>
> The first patch addresses issues found in the bmc_present and
> bmc_tcam_reinit handling. It started out addressing the fact that present
> w/o a MAC address was flagged as an invalid message. However, we ended up
> also addressing a potential race in that setting bmc_present and
> need_bmc_tcam_reinit could potentially race against the bmc_rpc_check. To
> address that the bit flags were moved to a state bitmap and are now handled
> via the test_and_clear_bit and assign_bit operations.
>
> [...]
Here is the summary with links:
- [next-next,v2,1/2] fbnic: Rework the BMC state pulled from the capabilities message
https://git.kernel.org/netdev/net-next/c/d261a371e3b7
- [next-next,v2,2/2] fbnic: Remove BMC routing rules when the BMC channel is disabled
https://git.kernel.org/netdev/net-next/c/db99b6fae21c
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-10-02 1:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 16:12 [next-next PATCH v2 0/2] eth: fbnic: Update BMC MAC address handling Alexander Duyck
2026-09-28 16:12 ` [next-next PATCH v2 1/2] fbnic: Rework the BMC state pulled from the capabilities message Alexander Duyck
2026-09-30 22:12 ` netdev-bot+sashiko
2026-10-01 20:03 ` Alexander Duyck
2026-09-28 16:12 ` [next-next PATCH v2 2/2] fbnic: Remove BMC routing rules when the BMC channel is disabled Alexander Duyck
2026-09-30 22:12 ` netdev-bot+sashiko
2026-10-01 20:23 ` Alexander Duyck
2026-09-28 16:15 ` [next-next PATCH v2 0/2] eth: fbnic: Update BMC MAC address handling netdev-bot+sinfo
2026-09-28 17:52 ` Alexander Duyck
2026-10-02 1:20 ` 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=179090401002.3168550.17513563940881597735.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox