From: Chen Gang <gang.chen@asianux•com>
To: David Miller <davem@davemloft•net>
Cc: edumazet@google•com, dborkman@redhat•com, wad@chromium•org,
eparis@redhat•com, netdev@vger•kernel.org
Subject: Re: [PATCH v2] include/linux: printk is needed in filter.h when CONFIG_BPF_JIT is defined
Date: Sat, 30 Mar 2013 11:41:58 +0800 [thread overview]
Message-ID: <51565F06.8070608@asianux.com> (raw)
In-Reply-To: <20130329.233220.2002219172165994260.davem@davemloft.net>
On 2013年03月30日 11:32, David Miller wrote:
> From: Chen Gang <gang.chen@asianux•com>
> Date: Sat, 30 Mar 2013 11:10:55 +0800
>
>> > On 2013^[$BG/^[(B03^[$B7n^[(B30^[$BF|^[(B 03:34, David Miller wrote:
>>> >> From: Chen Gang <gang.chen@asianux•com>
>>> >> Date: Fri, 29 Mar 2013 09:24:53 +0800
>>> >>
>>>>> >>> >
>>>>> >>> > 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>
>>> >> There are no references to pr_err nor print_hex_dump in this
>>> >> filter.h header file.
>> >
>> > maybe we see the different tree.
>> > I find it in next-20130328.
> When you submit patches, always mention explicitly what tree you
> want the patch applied to.
>
> In this case, this appropriate tree to be "net-next" since that
> is the tree where the problem actually exists.
I should notice, next time.
>
> Patch applied, thanks.
>
>
thanks, too.
--
Chen Gang
Asianux Corporation
next prev parent reply other threads:[~2013-03-30 3:42 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 ` [PATCH v2] include/linux: printk is needed in filter.h when CONFIG_BPF_JIT is defined Chen Gang
2013-03-29 19:34 ` David Miller
2013-03-30 3:10 ` Chen Gang
2013-03-30 3:32 ` David Miller
2013-03-30 3:41 ` Chen Gang [this message]
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=51565F06.8070608@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