From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
willemdebruijn.kernel@gmail.com, jasowang@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org, jdamato@fastly.com,
kory.maincent@bootlin.com, kuniyu@amazon.com, atenart@kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: bring back dev_addr_sem
Date: Wed, 19 Mar 2025 18:00:35 +0000 [thread overview]
Message-ID: <174240723503.1136881.3874262773936408000.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250312190513.1252045-1-sdf@fomichev.me>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 12 Mar 2025 12:05:11 -0700 you wrote:
> Kohei reports an issue with dev_addr_sem conversion to netdev instance
> lock in [0]. Based on the discussion, switching to netdev instance
> lock to protect the address might not work for the devices that
> are not using netdev ops lock.
> Bring dev_addr_sem instance lock back but fix the ordering.
>
> 0: https://lore.kernel.org/netdev/20250308203835.60633-2-enjuk@amazon.com
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] Revert "net: replace dev_addr_sem with netdev instance lock"
https://git.kernel.org/netdev/net-next/c/8033d2aef517
- [net-next,v2,2/2] net: reorder dev_addr_sem lock
https://git.kernel.org/netdev/net-next/c/6dd132516f8e
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-03-19 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 19:05 [PATCH net-next v2 0/2] net: bring back dev_addr_sem Stanislav Fomichev
2025-03-12 19:05 ` [PATCH net-next v2 1/2] Revert "net: replace dev_addr_sem with netdev instance lock" Stanislav Fomichev
2025-03-12 19:05 ` [PATCH net-next v2 2/2] net: reorder dev_addr_sem lock Stanislav Fomichev
2025-03-13 17:56 ` Kuniyuki Iwashima
2025-03-17 8:15 ` [PATCH net-next v2 0/2] net: bring back dev_addr_sem Lei Yang
2025-03-19 18: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=174240723503.1136881.3874262773936408000.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=jdamato@fastly.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=willemdebruijn.kernel@gmail.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