From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] libv4l: add missing bpf_common.h header
Date: Mon, 5 Nov 2018 21:59:27 +0100 [thread overview]
Message-ID: <20181105215927.2d4bd31a@gmx.net> (raw)
In-Reply-To: <20181103142810.7c8fe947@windsurf>
Hello Thomas,
On Sat, 3 Nov 2018 14:28:10 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello,
>
> On Fri, 2 Nov 2018 20:01:08 +0100, Peter Seiderer wrote:
> > Fixes [1] (for older toolchains not providing this header):
> >
> > CC keytable.o
> > In file included from bpf.h:26:0,
> > from keytable.c:37:
> > ../../include/linux/bpf.h:12:10: fatal error: linux/bpf_common.h: No such file or directory
> > #include <linux/bpf_common.h>
> > ^~~~~~~~~~~~~~~~~~~~
> >
> > [1] http://autobuild.buildroot.org/results/d22c0939eed4bc949f7eaeae7595d01ec45cc2cd
> >
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > ---
> > .../0005-Add-missing-linux-bpf_common.h.patch | 80 +++++++++++++++++++
> > 1 file changed, 80 insertions(+)
> > create mode 100644 package/libv4l/0005-Add-missing-linux-bpf_common.h.patch
>
> Applied to master, thanks. Could you submit this upstream? Thanks!
Yes, just done, see [1]...
Regards,
Peter
[1] https://www.mail-archive.com/linux-media at vger.kernel.org/msg136103.html
>
> Thomas
next prev parent reply other threads:[~2018-11-05 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 19:01 [Buildroot] [PATCH v1] libv4l: add missing bpf_common.h header Peter Seiderer
2018-11-03 13:28 ` Thomas Petazzoni
2018-11-05 20:59 ` Peter Seiderer [this message]
2018-11-06 20:01 ` Fabrice Fontaine
2018-11-06 22:32 ` Peter Seiderer
2018-11-07 16:59 ` Peter Korsgaard
2018-11-07 19:05 ` Fabrice Fontaine
2018-11-07 22:04 ` Peter Seiderer
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=20181105215927.2d4bd31a@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.