public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux•com>
To: edumazet@google•com, dborkman@redhat•com, wad@chromium•org,
	eparis@redhat•com
Cc: David Miller <davem@davemloft•net>, netdev <netdev@vger•kernel.org>
Subject: [PATCH v2] include/linux: printk is needed in filter.h when CONFIG_BPF_JIT is defined
Date: Fri, 29 Mar 2013 09:24:53 +0800	[thread overview]
Message-ID: <5154ED65.5090607@asianux.com> (raw)
In-Reply-To: <5153DC24.4010104@asianux.com>


  for make V=1 EXTRA_CFLAGS=-W ARCH=arm allmodconfig
    printk is need when CONFIG_BPF_JIT is defined
    or it will report pr_err and print_hex_dump are implicit declaration

Signed-off-by: Chen Gang <gang.chen@asianux•com>
---
 include/linux/filter.h |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/include/linux/filter.h b/include/linux/filter.h
index d7d2508..d1248f4 100644
--- a/include/linux/filter.h
+++ b/include/linux/filter.h
@@ -48,6 +48,9 @@ extern int sk_chk_filter(struct sock_filter *filter, unsigned int flen);
 extern int sk_get_filter(struct sock *sk, struct sock_filter __user *filter, unsigned len);
 
 #ifdef CONFIG_BPF_JIT
+#include <linux/linkage.h>
+#include <linux/printk.h>
+
 extern void bpf_jit_compile(struct sk_filter *fp);
 extern void bpf_jit_free(struct sk_filter *fp);
 
-- 
1.7.7.6

       reply	other threads:[~2013-03-29  2:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5153DC24.4010104@asianux.com>
2013-03-29  1:24 ` Chen Gang [this message]
2013-03-29 19:34   ` [PATCH v2] include/linux: printk is needed in filter.h when CONFIG_BPF_JIT is defined David Miller
2013-03-30  3:10     ` Chen Gang
2013-03-30  3:32       ` David Miller
2013-03-30  3:41         ` Chen Gang
2013-03-30  3:17     ` Chen Gang

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=5154ED65.5090607@asianux.com \
    --to=gang.chen@asianux$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=dborkman@redhat$(echo .)com \
    --cc=edumazet@google$(echo .)com \
    --cc=eparis@redhat$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=wad@chromium$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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