From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, marcelo.leitner@gmail.com,
nhorman@tuxdriver.com, dsahern@gmail.com, colrack@gmail.com
Subject: Re: [PATCHv2 net-next 0/7] sctp: support vrf processing
Date: Fri, 18 Nov 2022 12:00:25 +0000 [thread overview]
Message-ID: <166877282566.14131.2810734964750035632.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1668628394.git.lucien.xin@gmail.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 16 Nov 2022 15:01:15 -0500 you wrote:
> This patchset adds the VRF processing in SCTP. Simliar to TCP/UDP,
> it includes socket bind and socket/association lookup changes.
>
> For socket bind change, it allows sockets to bind to a VRF device
> and allows multiple sockets with the same IP and PORT to bind to
> different interfaces in patch 1-3.
>
> [...]
Here is the summary with links:
- [PATCHv2,net-next,1/7] sctp: verify the bind address with the tb_id from l3mdev
https://git.kernel.org/netdev/net-next/c/26943aefa870
- [PATCHv2,net-next,2/7] sctp: check ipv6 addr with sk_bound_dev if set
https://git.kernel.org/netdev/net-next/c/6fe1e52490a9
- [PATCHv2,net-next,3/7] sctp: check sk_bound_dev_if when matching ep in get_port
https://git.kernel.org/netdev/net-next/c/f87b1ac06c88
- [PATCHv2,net-next,4/7] sctp: add skb_sdif in struct sctp_af
https://git.kernel.org/netdev/net-next/c/33e93ed2209d
- [PATCHv2,net-next,5/7] sctp: add dif and sdif check in asoc and ep lookup
https://git.kernel.org/netdev/net-next/c/0af03170637f
- [PATCHv2,net-next,6/7] sctp: add sysctl net.sctp.l3mdev_accept
https://git.kernel.org/netdev/net-next/c/b712d0328c2c
- [PATCHv2,net-next,7/7] selftests: add a selftest for sctp vrf
https://git.kernel.org/netdev/net-next/c/a61bd7b9fef3
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-11-18 12:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 20:01 [PATCHv2 net-next 0/7] sctp: support vrf processing Xin Long
2022-11-16 20:01 ` [PATCHv2 net-next 1/7] sctp: verify the bind address with the tb_id from l3mdev Xin Long
2022-11-16 20:01 ` [PATCHv2 net-next 2/7] sctp: check ipv6 addr with sk_bound_dev if set Xin Long
2022-11-16 20:01 ` [PATCHv2 net-next 3/7] sctp: check sk_bound_dev_if when matching ep in get_port Xin Long
2022-11-16 20:01 ` [PATCHv2 net-next 4/7] sctp: add skb_sdif in struct sctp_af Xin Long
2022-11-16 20:01 ` [PATCHv2 net-next 5/7] sctp: add dif and sdif check in asoc and ep lookup Xin Long
2022-11-16 20:01 ` [PATCHv2 net-next 6/7] sctp: add sysctl net.sctp.l3mdev_accept Xin Long
2022-11-16 20:01 ` [PATCHv2 net-next 7/7] selftests: add a selftest for sctp vrf Xin Long
2022-11-18 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=166877282566.14131.2810734964750035632.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=colrack@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=pabeni@redhat.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.