From: David Miller <davem@davemloft.net>
To: rdunlap@infradead.org
Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH -next] net: fix test_bpf build to depend on NET
Date: Tue, 13 May 2014 13:16:01 -0400 (EDT) [thread overview]
Message-ID: <20140513.131601.2024599128071503735.davem@davemloft.net> (raw)
In-Reply-To: <53724F44.2010608@infradead.org>
From: Randy Dunlap <rdunlap@infradead.org>
Date: Tue, 13 May 2014 09:58:44 -0700
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix build when CONFIG_NET is not enabled.
> Fixes these build errors:
>
> WARNING: "sk_unattached_filter_destroy" [lib/test_bpf.ko] undefined!
> WARNING: "kfree_skb" [lib/test_bpf.ko] undefined!
> WARNING: "sk_unattached_filter_create" [lib/test_bpf.ko] undefined!
> WARNING: "sk_run_filter_int_skb" [lib/test_bpf.ko] undefined!
> WARNING: "__alloc_skb" [lib/test_bpf.ko] undefined!
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Applied, thanks Randy.
prev parent reply other threads:[~2014-05-13 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 16:58 [PATCH -next] net: fix test_bpf build to depend on NET Randy Dunlap
2014-05-13 17:04 ` Alexei Starovoitov
2014-05-13 17:16 ` 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=20140513.131601.2024599128071503735.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.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).