From: patchwork-bot+netdevbpf@kernel.org
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/5] dpaa2-switch: FDB management refactoring
Date: Sun, 14 Jun 2026 01:00:12 +0000 [thread overview]
Message-ID: <178139881214.1643025.15820072872565162202.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260610150912.1788482-1-ioana.ciornei@nxp.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 10 Jun 2026 18:09:07 +0300 you wrote:
> The FDB management done by the dpaa2_switch_port_set_fdb() function is
> hard to follow even by trained eyes. This series tries to make it easier
> to read and understand it by factoring out some code blocks into helper
> functions and unifying the join and leave paths in terms of FDB
> management.
>
> Ioana Ciornei (5):
> dpaa2-switch: change dpaa2_switch_port_set_fdb() function prototype
> dpaa2-switch: factor out the FDB in-use check into a helper
> dpaa2-switch: move FDB selection for join path into a helper
> dpaa2-switch: move FDB selection for leave path into a helper
> dpaa2-switch: unify the FDB update logic in
> dpaa2_switch_port_set_fdb()
>
> [...]
Here is the summary with links:
- [net-next,1/5] dpaa2-switch: change dpaa2_switch_port_set_fdb() function prototype
https://git.kernel.org/netdev/net-next/c/646077cc6b20
- [net-next,2/5] dpaa2-switch: factor out the FDB in-use check into a helper
https://git.kernel.org/netdev/net-next/c/5617bf8538ec
- [net-next,3/5] dpaa2-switch: move FDB selection for join path into a helper
https://git.kernel.org/netdev/net-next/c/e31f457ac7da
- [net-next,4/5] dpaa2-switch: move FDB selection for leave path into a helper
https://git.kernel.org/netdev/net-next/c/2230a2e62251
- [net-next,5/5] dpaa2-switch: unify the FDB update logic in dpaa2_switch_port_set_fdb()
https://git.kernel.org/netdev/net-next/c/7aae797a003e
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-06-14 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 15:09 [PATCH net-next 0/5] dpaa2-switch: FDB management refactoring Ioana Ciornei
2026-06-10 15:09 ` [PATCH net-next 1/5] dpaa2-switch: change dpaa2_switch_port_set_fdb() function prototype Ioana Ciornei
2026-06-10 15:09 ` [PATCH net-next 2/5] dpaa2-switch: factor out the FDB in-use check into a helper Ioana Ciornei
2026-06-10 15:09 ` [PATCH net-next 3/5] dpaa2-switch: move FDB selection for join path " Ioana Ciornei
2026-06-10 15:09 ` [PATCH net-next 4/5] dpaa2-switch: move FDB selection for leave " Ioana Ciornei
2026-06-10 15:09 ` [PATCH net-next 5/5] dpaa2-switch: unify the FDB update logic in dpaa2_switch_port_set_fdb() Ioana Ciornei
2026-06-14 1:00 ` 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=178139881214.1643025.15820072872565162202.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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