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
Subject: Re: [PATCH net-next 0/2] sctp: add some missing peer_capables in sctp info dump
Date: Mon, 17 Apr 2023 07:30:19 +0000 [thread overview]
Message-ID: <168171661951.7386.5828887285252600503.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1681507192.git.lucien.xin@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 14 Apr 2023 17:21:14 -0400 you wrote:
> The 1st patch removes the unused and obsolete hostname_address from
> sctp_association peer and also the bit from sctp_info peer_capables,
> and then reuses its bit for reconf_capable and use the higher
> available bit for intl_capable in the 2nd patch.
>
> Xin Long (2):
> sctp: delete the obsolete code for the host name address param
> sctp: add intl_capable and reconf_capable in ss peer_capable
>
> [...]
Here is the summary with links:
- [net-next,1/2] sctp: delete the obsolete code for the host name address param
https://git.kernel.org/netdev/net-next/c/bd4b28189469
- [net-next,2/2] sctp: add intl_capable and reconf_capable in ss peer_capable
https://git.kernel.org/netdev/net-next/c/ab4f1e28c941
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:[~2023-04-17 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 21:21 [PATCH net-next 0/2] sctp: add some missing peer_capables in sctp info dump Xin Long
2023-04-14 21:21 ` [PATCH net-next 1/2] sctp: delete the obsolete code for the host name address param Xin Long
2023-04-14 21:21 ` [PATCH net-next 2/2] sctp: add intl_capable and reconf_capable in ss peer_capable Xin Long
2023-04-17 7: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=168171661951.7386.5828887285252600503.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--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=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 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 read-only IMAP folder(s) and NNTP newsgroup(s).