netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: yamada.masahiro@socionext.com
Cc: netdev@vger.kernel.org, linux@roeck-us.net,
	songliubraving@fb.com, ast@kernel.org, yhs@fb.com,
	linux-kernel@vger.kernel.org, kafai@fb.com, daniel@iogearbox.net
Subject: Re: [PATCH] bpfilter: re-add header search paths to tools include to fix build error
Date: Sat, 23 Feb 2019 13:36:41 -0800 (PST)	[thread overview]
Message-ID: <20190223.133641.660058928993735320.davem@davemloft.net> (raw)
In-Reply-To: <1550805799-24572-1-git-send-email-yamada.masahiro@socionext.com>

From: Masahiro Yamada <yamada.masahiro@socionext.com>
Date: Fri, 22 Feb 2019 12:23:19 +0900

> 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>

Applied to net-next.

      parent reply	other threads:[~2019-02-23 21:36 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
2019-02-23 21:36 ` 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=20190223.133641.660058928993735320.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.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=yamada.masahiro@socionext.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).