From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, jiri@resnulli.us,
j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net,
sridhar.samudrala@intel.com, stephen@networkplumber.org,
liali@redhat.com
Subject: Re: [PATCH net-next 0/3] net: add IFF_NO_ADDRCONF to prevent ipv6 addrconf
Date: Mon, 12 Dec 2022 23:30:17 +0000 [thread overview]
Message-ID: <167088781787.32014.12569414144216569163.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1670599241.git.lucien.xin@gmail.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 9 Dec 2022 10:21:37 -0500 you wrote:
> This patchset adds IFF_NO_ADDRCONF flag for dev->priv_flags
> to prevent ipv6 addrconf, as Jiri Pirko's suggestion.
>
> For Bonding it changes to use this flag instead of IFF_SLAVE
> flag in Patch 1, and for Teaming and Net Failover it sets
> this flag before calling dev_open() in Patch 2 and 3.
>
> [...]
Here is the summary with links:
- [net-next,1/3] net: add IFF_NO_ADDRCONF and use it in bonding to prevent ipv6 addrconf
https://git.kernel.org/netdev/net-next/c/8a321cf7becc
- [net-next,2/3] net: team: use IFF_NO_ADDRCONF flag to prevent ipv6 addrconf
https://git.kernel.org/netdev/net-next/c/0aa64df30b38
- [net-next,3/3] net: failover: use IFF_NO_ADDRCONF flag to prevent ipv6 addrconf
https://git.kernel.org/netdev/net-next/c/cb54d392279d
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:[~2022-12-12 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 15:21 [PATCH net-next 0/3] net: add IFF_NO_ADDRCONF to prevent ipv6 addrconf Xin Long
2022-12-09 15:21 ` [PATCH net-next 1/3] net: add IFF_NO_ADDRCONF and use it in bonding " Xin Long
2022-12-09 15:21 ` [PATCH net-next 2/3] net: team: use IFF_NO_ADDRCONF flag " Xin Long
2022-12-09 15:21 ` [PATCH net-next 3/3] net: failover: " Xin Long
2022-12-12 23:30 ` 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=167088781787.32014.12569414144216569163.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liali@redhat.com \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sridhar.samudrala@intel.com \
--cc=stephen@networkplumber.org \
--cc=vfalico@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.