From: patchwork-bot+netdevbpf@kernel.org
To: Maxim Galaganov <max@internet.ru>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org, martineau@kernel.org,
matttbe@kernel.org, lkft@linaro.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] selftests: net: ip_local_port_range: define IPPROTO_MPTCP
Date: Tue, 13 Feb 2024 01:10:25 +0000 [thread overview]
Message-ID: <170778662564.1111.991367114536257318.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240209132512.254520-1-max@internet.ru>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 9 Feb 2024 16:25:11 +0300 you wrote:
> Older glibc's netinet/in.h may leave IPPROTO_MPTCP undefined when
> building ip_local_port_range.c, that leads to "error: use of undeclared
> identifier 'IPPROTO_MPTCP'".
>
> Define IPPROTO_MPTCP in such cases, just like in other MPTCP selftests.
>
> Fixes: 122db5e3634b ("selftests/net: add MPTCP coverage for IP_LOCAL_PORT_RANGE")
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> Closes: https://lore.kernel.org/netdev/CA+G9fYvGO5q4o_Td_kyQgYieXWKw6ktMa-Q0sBu6S-0y3w2aEQ@mail.gmail.com/
> Signed-off-by: Maxim Galaganov <max@internet.ru>
>
> [...]
Here is the summary with links:
- [net] selftests: net: ip_local_port_range: define IPPROTO_MPTCP
https://git.kernel.org/netdev/net/c/c2b3ec36b422
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:[~2024-02-13 1:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 13:25 [PATCH net] selftests: net: ip_local_port_range: define IPPROTO_MPTCP Maxim Galaganov
2024-02-09 13:57 ` Matthieu Baerts
2024-02-12 18:39 ` Naresh Kamboju
2024-02-13 1:10 ` 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=170778662564.1111.991367114536257318.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-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft@linaro.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=max@internet.ru \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.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.