From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "David S . Miller" <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
Song Liu <songliubraving@fb.com>,
Alexei Starovoitov <ast@kernel.org>, Yonghong Song <yhs@fb.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Martin KaFai Lau <kafai@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH] bpfilter: re-add header search paths to tools include to fix build error
Date: Fri, 22 Feb 2019 17:23:48 +0900 [thread overview]
Message-ID: <CAK7LNASvqCW9iK3MSYpjKnvYmaXdwrW+3E4S3pe0A_ugmUmQ2A@mail.gmail.com> (raw)
In-Reply-To: <80b08bfa-8052-aebb-db43-c7cbf3f5dd9d@roeck-us.net>
On Fri, Feb 22, 2019 at 2:55 PM Guenter Roeck <linux@roeck-us.net> wrote:
>
> On 2/21/19 7:23 PM, Masahiro Yamada wrote:
> > I thought header search paths to tools/include(/uapi) were unneeded,
> > but it looks like a build error occurs depending on the compiler.
> >
> > Commit 303a339f30a9 ("bpfilter: remove extra header search paths for
> > bpfilter_umh") reintroduced the build error fixed by commit ae40832e53c3
> > ("bpfilter: fix a build err").
> >
> > Apology for the breakage, and thanks to Guenter for reporting this.
> >
> > Fixes: 303a339f30a9 ("bpfilter: remove extra header search paths for bpfilter_umh")
> > Reported-by: Guenter Roeck <linux@roeck-us.net>
> > Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
>
> Tested-by: Guenter Roeck <linux@roeck-us.net>
Thank you!
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2019-02-22 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 3:23 [PATCH] bpfilter: re-add header search paths to tools include to fix build error Masahiro Yamada
2019-02-22 5:54 ` Guenter Roeck
2019-02-22 8:23 ` Masahiro Yamada [this message]
2019-02-23 21:36 ` 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=CAK7LNASvqCW9iK3MSYpjKnvYmaXdwrW+3E4S3pe0A_ugmUmQ2A@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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).