From: patchwork-bot+netdevbpf@kernel.org
To: John Wang <wangzq.jn@gmail.com>
Cc: jk@codeconstruct.com.au, matt@codeconstruct.com.au,
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 v2] net: mctp: Consistent peer address handling in ioctl tag allocation
Date: Fri, 02 Aug 2024 01:10:31 +0000 [thread overview]
Message-ID: <172256103107.22370.6605828738753325393.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240730084636.184140-1-wangzhiqiang02@ieisystem.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 30 Jul 2024 16:46:35 +0800 you wrote:
> When executing ioctl to allocate tags, if the peer address is 0,
> mctp_alloc_local_tag now replaces it with 0xff. However, during tag
> dropping, this replacement is not performed, potentially causing the key
> not to be dropped as expected.
>
> Signed-off-by: John Wang <wangzhiqiang02@ieisystem.com>
>
> [...]
Here is the summary with links:
- [net-next,v2] net: mctp: Consistent peer address handling in ioctl tag allocation
https://git.kernel.org/netdev/net-next/c/5fcf0801ef5c
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-08-02 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 8:46 [PATCH net-next v2] net: mctp: Consistent peer address handling in ioctl tag allocation John Wang
2024-08-01 15:57 ` Jakub Kicinski
2024-08-02 0:21 ` Jeremy Kerr
2024-08-02 1:05 ` Jakub Kicinski
2024-08-02 1:10 ` 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=172256103107.22370.6605828738753325393.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wangzq.jn@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 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.