From: David Ahern <dsahern@gmail.com>
To: David Miller <davem@davemloft.net>, andreas.a.roeseler@gmail.com
Cc: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org, kuba@kernel.org,
dsahern@kernel.org
Subject: Re: [PATCH V4 net-next 5/5] icmp: add response to RFC 8335 PROBE messages
Date: Wed, 17 Mar 2021 21:24:58 -0600 [thread overview]
Message-ID: <34107111-5293-2119-cfc7-8156c43ae555@gmail.com> (raw)
In-Reply-To: <20210317.201948.1069484608502867994.davem@davemloft.net>
On 3/17/21 9:19 PM, David Miller wrote:
> From: Andreas Roeseler <andreas.a.roeseler@gmail.com>
> Date: Wed, 17 Mar 2021 22:11:47 -0500
>
>> On Mon, 2021-03-15 at 04:35 +0800, kernel test robot wrote:
>> Is there something that I'm not understanding about compiling kernel
>> components modularly? How do I avoid this error?
>
>>
> You cannot reference module exported symbols from statically linked code.
> y
>
Look at ipv6_stub to see how it exports IPv6 functions for v4 code.
There are a few examples under net/ipv4.
next prev parent reply other threads:[~2021-03-18 3:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 16:48 [PATCH V4 net-next 0/5] add support for RFC 8335 PROBE Andreas Roeseler
2021-03-14 16:48 ` [PATCH V4 net-next 1/5] icmp: " Andreas Roeseler
2021-03-14 16:48 ` [PATCH V4 net-next 2/5] ICMPV6: " Andreas Roeseler
2021-03-14 16:48 ` [PATCH V4 net-next 3/5] net: add sysctl for enabling RFC 8335 PROBE messages Andreas Roeseler
2021-03-14 16:48 ` [PATCH V4 net-next 4/5] net: add support for sending " Andreas Roeseler
2021-03-14 16:48 ` [PATCH V4 net-next 5/5] icmp: add response to " Andreas Roeseler
2021-03-15 15:50 ` Willem de Bruijn
2021-03-15 19:09 ` Andreas Roeseler
2021-03-15 19:34 ` Willem de Bruijn
[not found] ` <202103150433.OwOTmI15-lkp@intel.com>
2021-03-18 3:11 ` Andreas Roeseler
2021-03-18 3:19 ` David Miller
2021-03-18 3:24 ` David Ahern [this message]
2021-03-20 16:01 ` Andreas Roeseler
2021-03-20 16:43 ` David Ahern
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=34107111-5293-2119-cfc7-8156c43ae555@gmail.com \
--to=dsahern@gmail.com \
--cc=andreas.a.roeseler@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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 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).