From: Stephen Hemminger <stephen@networkplumber.org>
To: Aaron Conole <aconole@redhat.com>
Cc: dev@openvswitch.org, netdev@vger.kernel.org,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Eelco Chaudron" <echaudro@redhat.com>,
"Ilya Maximets" <i.maximets@ovn.org>,
"Adrián Moreno" <amorenoz@redhat.com>,
"Mike Pattrick" <mpattric@redhat.com>,
"Florian Westphal" <fw@strlen.de>,
"John Fastabend" <john.fastabend@gmail.com>,
"Jakub Sitnicki" <jakub@cloudflare.com>,
"Joe Stringer" <joe@ovn.org>
Subject: Re: [RFC] net: openvswitch: Inroduce a light-weight socket map concept.
Date: Fri, 27 Jun 2025 14:55:32 -0700 [thread overview]
Message-ID: <20250627145532.500a3ae3@hermes.local> (raw)
In-Reply-To: <20250627210054.114417-1-aconole@redhat.com>
On Fri, 27 Jun 2025 17:00:54 -0400
Aaron Conole <aconole@redhat.com> wrote:
> diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c
> index 429fb34b075e..f43f905b1cb0 100644
> --- a/net/ipv4/tcp_ipv4.c
> +++ b/net/ipv4/tcp_ipv4.c
> @@ -93,6 +93,7 @@ static int tcp_v4_md5_hash_hdr(char *md5_hash, const struct tcp_md5sig_key *key,
> #endif
>
> struct inet_hashinfo tcp_hashinfo;
> +EXPORT_SYMBOL(tcp_hashinfo);
EXPORT_SYMBOL_GPL seems better here
next prev parent reply other threads:[~2025-06-27 21:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 21:00 [RFC] net: openvswitch: Inroduce a light-weight socket map concept Aaron Conole
2025-06-27 21:55 ` Stephen Hemminger [this message]
2025-06-30 10:07 ` Eric Dumazet
2025-06-30 12:13 ` Aaron Conole
2025-06-30 12:13 ` Aaron Conole
2025-06-28 16:20 ` Cong Wang
2025-06-30 12:34 ` Aaron Conole
2025-07-10 9:18 ` Adrián Moreno
2025-07-04 14:22 ` Eelco Chaudron
2025-07-10 20:58 ` Aaron Conole
2025-07-10 9:35 ` Adrián Moreno
2025-07-10 21:07 ` Aaron Conole
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=20250627145532.500a3ae3@hermes.local \
--to=stephen@networkplumber.org \
--cc=aconole@redhat.com \
--cc=amorenoz@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=i.maximets@ovn.org \
--cc=jakub@cloudflare.com \
--cc=joe@ovn.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=mpattric@redhat.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 NNTP newsgroup(s).