From: Thomas Monjalon <thomas@monjalon.net>
To: Ophir Munk <ophirmu@mellanox.com>
Cc: dev@dpdk.org, Pascal Mazon <pascal.mazon@6wind.com>,
Olga Shern <olgas@mellanox.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Viktorin <viktorin@rehivetech.com>,
Jianbo Liu <jianbo.liu@arm.com>
Subject: Re: [dpdk-dev] [PATCH v1] net/tap: fix build on ARM
Date: Wed, 31 Jan 2018 19:10:52 +0100 [thread overview]
Message-ID: <1827276.i0qRTdFd37@xps> (raw)
In-Reply-To: <1517414638-29180-1-git-send-email-ophirmu@mellanox.com>
31/01/2018 17:03, Ophir Munk:
> This commit adds eBPF system call definitions for ARM architecture.
> Old Linux header files may not define eBPF system call numbers.
> In order to successful compile eBPF on all Linux platforms - the
> missing ARM system call definition is explicitly added.
>
> Fixes: b02d85e1 ("net/tap: add eBPF API")
>
> Signed-off-by: Ophir Munk <ophirmu@mellanox.com>
Note: it is only for ARM32.
Applied, thanks
prev parent reply other threads:[~2018-01-31 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 16:03 Ophir Munk
2018-01-31 18:10 ` Thomas Monjalon [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=1827276.i0qRTdFd37@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianbo.liu@arm.com \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.com \
--cc=pascal.mazon@6wind.com \
--cc=viktorin@rehivetech.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).