From: Markos Chandras <Markos.Chandras@imgtec.com>
To: David Miller <davem@davemloft.net>
Cc: <linux-kernel@vger.kernel.org>, <dborkman@redhat.com>
Subject: Re: [PATCH v2] tools/net/Makefile: Define PACKAGE to fix build problems
Date: Tue, 11 Mar 2014 08:43:06 +0000 [thread overview]
Message-ID: <531ECC9A.8000808@imgtec.com> (raw)
In-Reply-To: <20140310.215352.573291450790920864.davem@davemloft.net>
On 03/11/2014 01:53 AM, David Miller wrote:
> From: Markos Chandras <markos.chandras@imgtec.com>
> Date: Mon, 10 Mar 2014 10:39:48 +0000
>
>> Fixes the following build problem with binutils-2.24
>>
>> gcc -Wall -O2 -c -o bpf_jit_disasm.o bpf_jit_disasm.c
>> In file included from bpf_jit_disasm.c:25:0:
>> /usr/include/bfd.h:35:2: error: #error config.h must be included
>> before this header
>> #error config.h must be included before this header
>>
>> This is similar to commit 3ce711a6abc27abce1554e1d671a8762b7187690
>> "perf tools: bfd.h/libbfd detection fails with recent binutils"
>>
>> See: https://sourceware.org/bugzilla/show_bug.cgi?id=14243
>>
>> CC: David S. Miller <davem@davemloft.net>
>> CC: Daniel Borkmann <dborkman@redhat.com>
>> Acked-by: Daniel Borkmann <dborkman@redhat.com>
>> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
>
> Please submit networking patches with netdev@vger.kernel.org at least
> CC:'d so that such patches can be properly tracked in patchwork.
>
> Thank you.
>
Hi David,
Apologies. When I ran the scripts/get_maintainer.pl on my patch,
netdev@vger.kernel.org was not listed there. I will send it again.
--
markos
next prev parent reply other threads:[~2014-03-11 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 10:39 Markos Chandras
2014-03-11 1:53 ` David Miller
2014-03-11 8:43 ` Markos Chandras [this message]
2014-03-11 8:49 ` Markos Chandras
2014-03-12 4:08 ` 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=531ECC9A.8000808@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®