From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for Nov 10 (net/ipv4/ip_tunnel.c)
Date: Mon, 10 Nov 2014 10:15:11 -0800 [thread overview]
Message-ID: <546100AF.40201@infradead.org> (raw)
In-Reply-To: <20141110205945.51af32a6@canb.auug.org.au>
On 11/10/14 01:59, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20141106:
>
on x86_64:
when CONFIG_NET_IP_TUNNEL=y and CONFIG_NET_FOU=m:
net/built-in.o: In function `ip_tunnel_encap':
(.text+0xb04d8): undefined reference to `gue_build_header'
net/built-in.o: In function `ip_tunnel_encap':
(.text+0xb04ea): undefined reference to `fou_build_header'
--
~Randy
next parent reply other threads:[~2014-11-10 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141110205945.51af32a6@canb.auug.org.au>
2014-11-10 18:15 ` Randy Dunlap [this message]
2014-11-10 19:24 ` linux-next: Tree for Nov 10 (net/ipv4/ip_tunnel.c) David Miller
2014-11-10 20:29 ` Tom Herbert
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=546100AF.40201@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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;
as well as URLs for NNTP newsgroup(s).