From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <edumazet@google.com>
Cc: <davem@davemloft.net>, <eric.dumazet@gmail.com>,
<horms@kernel.org>, <kuba@kernel.org>, <kuniyu@amazon.com>,
<mateusz.polchlopek@intel.com>, <ncardwell@google.com>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<sd@queasysnail.net>, <willemb@google.com>
Subject: Re: [PATCH v2 net-next 1/4] net: introduce EXPORT_IPV6_MOD() and EXPORT_IPV6_MOD_GPL()
Date: Thu, 13 Feb 2025 12:51:08 +0900 [thread overview]
Message-ID: <20250213035108.85647-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20250212132418.1524422-2-edumazet@google.com>
From: Eric Dumazet <edumazet@google.com>
Date: Wed, 12 Feb 2025 13:24:15 +0000
> We have many EXPORT_SYMBOL(x) in networking tree because IPv6
> can be built as a module.
>
> CONFIG_IPV6=y is becoming the norm.
>
> Define a EXPORT_IPV6_MOD(x) which only exports x
> for modular IPv6.
>
> Same principle applies to EXPORT_IPV6_MOD_GPL()
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>
next prev parent reply other threads:[~2025-02-13 3:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 13:24 [PATCH v2 net-next 0/4] net: add EXPORT_IPV6_MOD() Eric Dumazet
2025-02-12 13:24 ` [PATCH v2 net-next 1/4] net: introduce EXPORT_IPV6_MOD() and EXPORT_IPV6_MOD_GPL() Eric Dumazet
2025-02-13 3:51 ` Kuniyuki Iwashima [this message]
2025-02-13 7:26 ` Mateusz Polchlopek
2025-02-12 13:24 ` [PATCH v2 net-next 2/4] inetpeer: use EXPORT_IPV6_MOD[_GPL]() Eric Dumazet
2025-02-13 3:53 ` Kuniyuki Iwashima
2025-02-13 7:26 ` Mateusz Polchlopek
2025-02-12 13:24 ` [PATCH v2 net-next 3/4] tcp: " Eric Dumazet
2025-02-13 4:20 ` Kuniyuki Iwashima
2025-02-13 7:27 ` Mateusz Polchlopek
2025-02-12 13:24 ` [PATCH v2 net-next 4/4] udp: " Eric Dumazet
2025-02-12 17:11 ` Willem de Bruijn
2025-02-13 7:28 ` Mateusz Polchlopek
2025-02-14 21:30 ` [PATCH v2 net-next 0/4] net: add EXPORT_IPV6_MOD() patchwork-bot+netdevbpf
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=20250213035108.85647-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=mateusz.polchlopek@intel.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--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 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.