From: patchwork-bot+netdevbpf@kernel•org
To: Gou Hao <gouhao@uniontech•com>
Cc: davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, kuniyu@amazon•com, wuyun.abel@bytedance•com,
leitao@debian•org, alexander@mihalicyn•com, dhowells@redhat•com,
netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
zhanjun@uniontech•com, gouhaojake@163•com
Subject: Re: [PATCH 1/2] net/core: remove redundant sk_callback_lock initialization
Date: Tue, 28 May 2024 12:00:30 +0000 [thread overview]
Message-ID: <171689763075.20900.865720577664819841.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240526145718.9542-1-gouhao@uniontech.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat•com>:
On Sun, 26 May 2024 22:57:17 +0800 you wrote:
> sk_callback_lock has already been initialized in sk_init_common().
>
> Signed-off-by: Gou Hao <gouhao@uniontech•com>
> ---
> net/core/sock.c | 1 -
> 1 file changed, 1 deletion(-)
Here is the summary with links:
- [1/2] net/core: remove redundant sk_callback_lock initialization
https://git.kernel.org/netdev/net-next/c/c65b6521115e
- [2/2] net/core: move the lockdep-init of sk_callback_lock to sk_init_common()
https://git.kernel.org/netdev/net-next/c/de31e96cf423
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:[~2024-05-28 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-26 14:57 [PATCH 1/2] net/core: remove redundant sk_callback_lock initialization Gou Hao
2024-05-26 14:57 ` [PATCH 2/2] net/core: move the lockdep-init of sk_callback_lock to sk_init_common() Gou Hao
2024-05-28 8:00 ` [PATCH 1/2] net/core: remove redundant sk_callback_lock initialization Breno Leitao
2024-05-28 12: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=171689763075.20900.865720577664819841.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=alexander@mihalicyn$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dhowells@redhat$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=gouhao@uniontech$(echo .)com \
--cc=gouhaojake@163$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kuniyu@amazon$(echo .)com \
--cc=leitao@debian$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=wuyun.abel@bytedance$(echo .)com \
--cc=zhanjun@uniontech$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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