From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: linux-next: Tree for Nov 17 (uml, no IPV6)
Date: Tue, 16 Nov 2021 21:46:35 -0800 [thread overview]
Message-ID: <268ae204-efae-3081-a5dd-44fc07d048ba@infradead.org> (raw)
In-Reply-To: <20211117135800.0b7072cd@canb.auug.org.au>
On 11/16/21 6:58 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20211116:
>
ARCH=um SUBARCH=x86_64:
# CONFIG_IPV6 is not set
In file included from ../net/ethernet/eth.c:62:0:
../include/net/gro.h: In function ‘ip6_gro_compute_pseudo’:
../include/net/gro.h:413:22: error: implicit declaration of function ‘csum_ipv6_magic’; did you mean ‘csum_tcpudp_magic’? [-Werror=implicit-function-declaration]
return ~csum_unfold(csum_ipv6_magic(&iph->saddr, &iph->daddr,
^~~~~~~~~~~~~~~
csum_tcpudp_magic
After I made ip6_gro_compute_pseudo() conditional on CONFIG_IPV6,
I got this build error:
In file included from ../net/ipv6/tcpv6_offload.c:10:0:
../net/ipv6/tcpv6_offload.c: In function ‘tcp6_gro_receive’:
../net/ipv6/tcpv6_offload.c:22:11: error: implicit declaration of function ‘ip6_gro_compute_pseudo’; did you mean ‘inet_gro_compute_pseudo’? [-Werror=implicit-function-declaration]
ip6_gro_compute_pseudo)) {
^
../include/net/gro.h:235:5: note: in definition of macro ‘__skb_gro_checksum_validate’
compute_pseudo(skb, proto)); \
^~~~~~~~~~~~~~
../net/ipv6/tcpv6_offload.c:21:6: note: in expansion of macro ‘skb_gro_checksum_validate’
skb_gro_checksum_validate(skb, IPPROTO_TCP,
^~~~~~~~~~~~~~~~~~~~~~~~~
This is UML x86_64 defconfig:
$ make ARCH=um SUBARCH=x86_64 defconfig all
--
~Randy
next prev parent reply other threads:[~2021-11-17 5:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 2:58 linux-next: Tree for Nov 17 Stephen Rothwell
2021-11-17 5:46 ` Randy Dunlap [this message]
2021-11-17 8:44 ` linux-next: Tree for Nov 17 (uml, no IPV6) Geert Uytterhoeven
2021-11-17 9:38 ` Eric Dumazet
2021-11-17 9:46 ` Geert Uytterhoeven
2021-11-17 9:50 ` Eric Dumazet
2021-11-17 9:55 ` Eric Dumazet
2021-11-17 10:04 ` Geert Uytterhoeven
2021-11-17 10:05 ` Eric Dumazet
2021-11-17 22:23 ` linux-next: Tree for Nov 17 (fs/dlm/lowcomms.c) Randy Dunlap
2021-11-18 8:26 ` Geert Uytterhoeven
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=268ae204-efae-3081-a5dd-44fc07d048ba@infradead.org \
--to=rdunlap@infradead.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®