From: akuster808 <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][jethro[master]][meta-networking] netmap-modules: fix build with kernel < 3.17
Date: Wed, 30 Dec 2015 19:20:53 -0800 [thread overview]
Message-ID: <56849F15.4090003@gmail.com> (raw)
In-Reply-To: <1451491343-27865-1-git-send-email-Martin.Jansa@gmail.com>
will pull this shortly.
- armin
On 12/30/2015 08:02 AM, Martin Jansa wrote:
> * define NETMAP_LINUX_ALLOC_NETDEV_4ARGS only when MACHINE is using kernel
> 3.17 or newer
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta-networking/recipes-kernel/netmap/netmap-modules_git.bb | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/meta-networking/recipes-kernel/netmap/netmap-modules_git.bb b/meta-networking/recipes-kernel/netmap/netmap-modules_git.bb
> index 6e6f02c..31fedbb 100644
> --- a/meta-networking/recipes-kernel/netmap/netmap-modules_git.bb
> +++ b/meta-networking/recipes-kernel/netmap/netmap-modules_git.bb
> @@ -61,7 +61,6 @@ do_configure_append () {
> #define NETMAP_LINUX_HAVE_PHYS_ADDR_T
> #define NETMAP_LINUX_HAVE_ACCESS_ONCE
> #define NETMAP_LINUX_HAVE_NETDEV_OPS
> -#define NETMAP_LINUX_ALLOC_NETDEV_4ARGS
> #define NETMAP_LINUX_HAVE_INIT_NET
> #define NETMAP_LINUX_HAVE_LIVE_ADDR_CHANGE
> #define NETMAP_LINUX_HAVE_TX_SKB_SHARING
> @@ -75,6 +74,13 @@ do_configure_append () {
> #define NETMAP_LINUX_HAVE_E1000E_EXT_RXDESC
> #define NETMAP_LINUX_HAVE_E1000E_DOWN2
> EOF
> +
> +if ${@ 'true' if (bb.utils.vercmp_string(d.getVar('KERNEL_VERSION', True), '3.17') < 0) else 'false' } ; then
> + echo OK
> + cat >> ${S}/LINUX/netmap_linux_config.h <<EOF
> +#define NETMAP_LINUX_ALLOC_NETDEV_4ARGS
> +EOF
> +fi
> }
>
> do_compile () {
>
prev parent reply other threads:[~2015-12-31 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 16:02 [PATCH][jethro[master]][meta-networking] netmap-modules: fix build with kernel < 3.17 Martin Jansa
2015-12-31 3:20 ` akuster808 [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=56849F15.4090003@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-devel@lists.openembedded.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