From: patchwork-bot+netdevbpf@kernel.org
To: Wen Gu <guwen@linux.alibaba.com>
Cc: wenjia@linux.ibm.com, jaka@linux.ibm.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
alibuda@linux.alibaba.com, tonylu@linux.alibaba.com,
horms@kernel.org, kgraul@linux.ibm.com, hwippel@linux.ibm.com,
linux-rdma@vger.kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] two fixes for SMC
Date: Tue, 03 Dec 2024 09:59:05 +0000 [thread overview]
Message-ID: <173321994523.4135237.6293056111747884412.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241127133014.100509-1-guwen@linux.alibaba.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 27 Nov 2024 21:30:12 +0800 you wrote:
> Hi, all
>
> This patch set contains two bugfixes, to fix SMC warning and panic
> issues in race conditions.
>
> Thanks!
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net/smc: initialize close_work early to avoid warning
https://git.kernel.org/netdev/net/c/0541db8ee32c
- [net,v2,2/2] net/smc: fix LGR and link use-after-free issue
https://git.kernel.org/netdev/net/c/2c7f14ed9c19
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-12-03 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 13:30 [PATCH net v2 0/2] two fixes for SMC Wen Gu
2024-11-27 13:30 ` [PATCH net v2 1/2] net/smc: initialize close_work early to avoid warning Wen Gu
2024-11-27 13:30 ` [PATCH net v2 2/2] net/smc: fix LGR and link use-after-free issue Wen Gu
2024-11-29 13:28 ` Alexandra Winter
2024-11-29 17:00 ` Wenjia Zhang
2024-12-03 9:59 ` 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=173321994523.4135237.6293056111747884412.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=hwippel@linux.ibm.com \
--cc=jaka@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).