From: patchwork-bot+netdevbpf@kernel.org
To: Yue Haibing <yuehaibing@huawei.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
kuniyu@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/2] ipv6: improve rpl_seg_enabled sysctl handling
Date: Wed, 03 Sep 2025 00:10:13 +0000 [thread overview]
Message-ID: <175685821323.475224.6132941673804776469.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250901123726.1972881-1-yuehaibing@huawei.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 1 Sep 2025 20:37:24 +0800 you wrote:
> First commit annotate data-races around it and second one add sanity check that
> prevents unintentional misconfiguration.
>
> Yue Haibing (2):
> ipv6: annotate data-races around devconf->rpl_seg_enabled
> ipv6: Add sanity checks on ipv6_devconf.rpl_seg_enabled
>
> [...]
Here is the summary with links:
- [v3,net-next,1/2] ipv6: annotate data-races around devconf->rpl_seg_enabled
https://git.kernel.org/netdev/net/c/3a5f55500f3e
- [v3,net-next,2/2] ipv6: Add sanity checks on ipv6_devconf.rpl_seg_enabled
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-09-03 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 12:37 [PATCH v3 net-next 0/2] ipv6: improve rpl_seg_enabled sysctl handling Yue Haibing
2025-09-01 12:26 ` Yue Haibing
2025-09-01 12:37 ` [PATCH v3 net-next 1/2] ipv6: annotate data-races around devconf->rpl_seg_enabled Yue Haibing
2025-09-01 12:37 ` [PATCH v3 net-next 2/2] ipv6: Add sanity checks on ipv6_devconf.rpl_seg_enabled Yue Haibing
2025-09-03 0:10 ` patchwork-bot+netdevbpf [this message]
2025-09-03 0:10 ` [PATCH v3 net-next 0/2] ipv6: improve rpl_seg_enabled sysctl handling patchwork-bot+netdevbpf
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=175685821323.475224.6132941673804776469.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=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yuehaibing@huawei.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