From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, kuni1840@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v1 net-next 0/2] net: Misc follow-up on RTNL-less fib_rules series.
Date: Tue, 07 Jul 2026 09:00:08 +0000 [thread overview]
Message-ID: <178341480863.1439689.8864452646287174123.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260702044437.591864-1-kuniyu@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 2 Jul 2026 04:44:13 +0000 you wrote:
> Patch 1 moves net->ipv4.fib_table_hash_lock under
> CONFIG_IP_MULTIPLE_TABLES.
>
> Patch 2 adds mutex_destroy() for fib_rules_ops.lock.
>
>
> Kuniyuki Iwashima (2):
> ipv4: fib: Define fib_table_hash_lock under CONFIG_IP_MULTIPLE_TABLES.
> net: fib_rules: Destroy ops->lock in fib_rules_unregister().
>
> [...]
Here is the summary with links:
- [v1,net-next,1/2] ipv4: fib: Define fib_table_hash_lock under CONFIG_IP_MULTIPLE_TABLES.
https://git.kernel.org/netdev/net-next/c/6041421dd087
- [v1,net-next,2/2] net: fib_rules: Destroy ops->lock in fib_rules_unregister().
https://git.kernel.org/netdev/net-next/c/99c13f8020df
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-07-07 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 4:44 [PATCH v1 net-next 0/2] net: Misc follow-up on RTNL-less fib_rules series Kuniyuki Iwashima
2026-07-02 4:44 ` [PATCH v1 net-next 1/2] ipv4: fib: Define fib_table_hash_lock under CONFIG_IP_MULTIPLE_TABLES Kuniyuki Iwashima
2026-07-02 7:17 ` Ido Schimmel
2026-07-02 4:44 ` [PATCH v1 net-next 2/2] net: fib_rules: Destroy ops->lock in fib_rules_unregister() Kuniyuki Iwashima
2026-07-02 7:18 ` Ido Schimmel
2026-07-07 9: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=178341480863.1439689.8864452646287174123.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--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 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.