From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Helin Zhang <helin.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] kni: fix vhost-kni compile errors
Date: Mon, 11 Apr 2016 19:04:10 +0200 [thread overview]
Message-ID: <1669957.aOl2YMNTtp@xps13> (raw)
In-Reply-To: <1460393668-17719-1-git-send-email-ferruh.yigit@intel.com>
2016-04-11 17:54, Ferruh Yigit:
> +#if LINUX_VERSION_CODE >= KERNEL_VERSION(4,4,0)
> + (!test_and_set_bit(SOCKWQ_ASYNC_NOSPACE, &q->sock->flags) &&
> +#else
> (!test_and_set_bit(SOCK_ASYNC_NOSPACE, &q->sock->flags) &&
> +#endif
You could avoid some issues with backported feature by using
#ifdef SOCKWQ_ASYNC_NOSPACE
next prev parent reply other threads:[~2016-04-11 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 23:26 [dpdk-dev] DPDK 2.2 build failing with vhost-kni chintu hetam
2016-04-11 8:25 ` Xie, Huawei
2016-04-11 14:09 ` chintu hetam
2016-04-11 18:57 ` chintu hetam
2016-04-11 19:02 ` chintu hetam
2016-04-11 16:54 ` [dpdk-dev] [PATCH] kni: fix vhost-kni compile errors Ferruh Yigit
2016-04-11 17:04 ` Thomas Monjalon [this message]
2016-04-11 17:57 ` Ferruh Yigit
2016-04-11 18:30 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2016-04-11 20:43 ` Thomas Monjalon
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=1669957.aOl2YMNTtp@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=helin.zhang@intel.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).