From: David Miller <davem@davemloft.net>
To: rdunlap@infradead.org
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
0xeffeff@gmail.com
Subject: Re: linux-next: Tree for Nov 5 (net/ipv6/af_inet6)
Date: Mon, 05 Nov 2018 10:12:09 -0800 (PST) [thread overview]
Message-ID: <20181105.101209.563084010777423448.davem@davemloft.net> (raw)
In-Reply-To: <2ad190b3-0b0d-972b-2a6e-16abf4a81c5b@infradead.org>
From: Randy Dunlap <rdunlap@infradead.org>
Date: Mon, 5 Nov 2018 08:21:28 -0800
> On 11/4/18 9:51 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20181102:
>>
>> Non-merge commits (relative to Linus' tree): 418
>
> on i386 or x86_64:
>
> ld: net/ipv6/af_inet6.o: in function `inet6_init':
> af_inet6.c:(.init.text+0x285): undefined reference to `ipv6_anycast_init'
> ld: af_inet6.c:(.init.text+0x376): undefined reference to `ipv6_anycast_cleanup'
>
>
> Full randconfig file is attached (for i386).
Jeff, please fix this.
prev parent reply other threads:[~2018-11-05 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181105165109.410358fd@canb.auug.org.au>
2018-11-05 16:21 ` linux-next: Tree for Nov 5 (net/ipv6/af_inet6) Randy Dunlap
2018-11-05 18:12 ` David Miller [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=20181105.101209.563084010777423448.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=0xeffeff@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).