From: patchwork-bot+netdevbpf@kernel.org
To: Andrea Claudi <aclaudi@redhat.com>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org, dsahern@gmail.com
Subject: Re: [PATCH iproute2-next 0/2] ss: remove implicit dependency on rpcinfo
Date: Thu, 24 Mar 2022 03:30:10 +0000 [thread overview]
Message-ID: <164809261064.4724.12273301402459681800.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1647455133.git.aclaudi@redhat.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Wed, 16 Mar 2022 19:52:12 +0100 you wrote:
> ss uses rpcinfo to get info about rpc service sockets. However, rpcinfo
> is not part of iproute2 and it's an implicit dependency for ss.
>
> This series uses libtirpc[1] API to implement the same feature of
> rpcinfo for ss. This makes it possible to get info about rpc sockets,
> provided ss is compiled with libtirpc support.
>
> [...]
Here is the summary with links:
- [iproute2-next,1/2] configure: add check_libtirpc()
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=1ee309a49aa0
- [iproute2-next,2/2] ss: remove an implicit dependency on rpcinfo
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=292509f95dd4
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-03-24 3:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 18:52 [PATCH iproute2-next 0/2] ss: remove implicit dependency on rpcinfo Andrea Claudi
2022-03-16 18:52 ` [PATCH iproute2-next 1/2] configure: add check_libtirpc() Andrea Claudi
2022-03-16 18:52 ` [PATCH iproute2-next 2/2] ss: remove an implicit dependency on rpcinfo Andrea Claudi
2022-03-24 3: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=164809261064.4724.12273301402459681800.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aclaudi@redhat.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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.