From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
stephen@networkplumber.org, hannes@stressinduktion.org,
willemb@google.com
Subject: Re: [PATCH net-next] uapi: in6: restore visibility of most IPv6 socket options
Date: Tue, 10 Jun 2025 22:00:34 +0000 [thread overview]
Message-ID: <174959283424.2624817.13317438796223681599.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250609143933.1654417-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 9 Jun 2025 07:39:33 -0700 you wrote:
> A decade ago commit 6d08acd2d32e ("in6: fix conflict with glibc")
> hid the definitions of IPV6 options, because GCC was complaining
> about duplicates. The commit did not list the warnings seen, but
> trying to recreate them now I think they are (building iproute2):
>
> In file included from ./include/uapi/rdma/rdma_user_cm.h:39,
> from rdma.h:16,
> from res.h:9,
> from res-ctx.c:7:
> ../include/uapi/linux/in6.h:171:9: warning: ‘IPV6_ADD_MEMBERSHIP’ redefined
> 171 | #define IPV6_ADD_MEMBERSHIP 20
> | ^~~~~~~~~~~~~~~~~~~
> In file included from /usr/include/netinet/in.h:37,
> from rdma.h:13:
> /usr/include/bits/in.h:233:10: note: this is the location of the previous definition
> 233 | # define IPV6_ADD_MEMBERSHIP IPV6_JOIN_GROUP
> | ^~~~~~~~~~~~~~~~~~~
> ../include/uapi/linux/in6.h:172:9: warning: ‘IPV6_DROP_MEMBERSHIP’ redefined
> 172 | #define IPV6_DROP_MEMBERSHIP 21
> | ^~~~~~~~~~~~~~~~~~~~
> /usr/include/bits/in.h:234:10: note: this is the location of the previous definition
> 234 | # define IPV6_DROP_MEMBERSHIP IPV6_LEAVE_GROUP
> | ^~~~~~~~~~~~~~~~~~~~
>
> [...]
Here is the summary with links:
- [net-next] uapi: in6: restore visibility of most IPv6 socket options
https://git.kernel.org/netdev/net-next/c/31557b3487b3
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:[~2025-06-10 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 14:39 [PATCH net-next] uapi: in6: restore visibility of most IPv6 socket options Jakub Kicinski
2025-06-10 22: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=174959283424.2624817.13317438796223681599.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hannes@stressinduktion.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.org \
--cc=willemb@google.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 NNTP newsgroup(s).