From: Daniel Borkmann <daniel@iogearbox.net>
To: Randy Dunlap <rdunlap@infradead.org>,
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 Mar 9 (net: bpf)
Date: Wed, 09 Mar 2016 17:48:19 +0100 [thread overview]
Message-ID: <56E053D3.7090009@iogearbox.net> (raw)
In-Reply-To: <56E052E4.90504@infradead.org>
On 03/09/2016 05:44 PM, Randy Dunlap wrote:
> On 03/08/16 21:38, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20160308:
>
> on x86_64:
>
> ../net/core/filter.c: In function 'bpf_skb_get_tunnel_opt':
> ../net/core/filter.c:1824:2: error: implicit declaration of function 'ip_tunnel_info_opts_get' [-Werror=implicit-function-declaration]
> ip_tunnel_info_opts_get(to, info);
> ^
> ../net/core/filter.c: In function 'bpf_skb_set_tunnel_opt':
> ../net/core/filter.c:1918:2: error: implicit declaration of function 'ip_tunnel_info_opts_set' [-Werror=implicit-function-declaration]
> ip_tunnel_info_opts_set(info, from, size);
> ^
> Full randconfig file is attached.
Already fixed with net-next commit e28e87ed474c ("ip_tunnel, bpf:
ip_tunnel_info_opts_{get, set} depends on CONFIG_INET").
Thanks,
Daniel
next prev parent reply other threads:[~2016-03-09 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160309163852.4dd159b1@canb.auug.org.au>
2016-03-09 16:44 ` linux-next: Tree for Mar 9 (net: bpf) Randy Dunlap
2016-03-09 16:48 ` Daniel Borkmann [this message]
2016-03-09 17:07 ` Randy Dunlap
2016-03-09 17:18 ` Randy Dunlap
2016-03-09 17:20 ` Daniel Borkmann
2016-03-09 17:19 ` Daniel Borkmann
2016-03-09 17:20 ` David Miller
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=56E053D3.7090009@iogearbox.net \
--to=daniel@iogearbox.net \
--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