From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: Jay Zhou <jianjay.zhou@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"Tan, Jianfeng" <jianfeng.tan@intel.com>,
"arei.gonglei@huawei.com" <arei.gonglei@huawei.com>,
"weidong.huang@huawei.com" <weidong.huang@huawei.com>,
"wangxinxin.wang@huawei.com" <wangxinxin.wang@huawei.com>
Subject: Re: [dpdk-dev] [PATCH] lib/librte_vhost: add virtio_crypto.h header file
Date: Thu, 5 Apr 2018 14:41:45 +0000 [thread overview]
Message-ID: <9F7182E3F746AB4EA17801C148F3C604331100E0@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <1522939053-11436-1-git-send-email-jianjay.zhou@huawei.com>
> -----Original Message-----
> From: Jay Zhou [mailto:jianjay.zhou@huawei.com]
> Sent: Thursday, April 5, 2018 3:38 PM
> To: dev@dpdk.org
> Cc: maxime.coquelin@redhat.com; Tan, Jianfeng <jianfeng.tan@intel.com>;
> Zhang, Roy Fan <roy.fan.zhang@intel.com>; arei.gonglei@huawei.com;
> weidong.huang@huawei.com; wangxinxin.wang@huawei.com;
> jianjay.zhou@huawei.com
> Subject: [PATCH] lib/librte_vhost: add virtio_crypto.h header file
>
> Since the linux kernel header file virtio_crypto.h has been merged in 4.9, if
> we include this header file directly, compilation will be failed in the old
> kernels' environment, e.g. the vhost crypto backend series.
> Adding virtio_crypto.h in librte_vhost to make old kernels happy.
>
> Signed-off-by: Jay Zhou <jianjay.zhou@huawei.com>
> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
>
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
Thanks a lot Jay.
next prev parent reply other threads:[~2018-04-05 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 14:37 Jay Zhou
2018-04-05 14:41 ` Zhang, Roy Fan [this message]
2018-04-05 19:21 ` Maxime Coquelin
2018-04-05 19:40 ` Maxime Coquelin
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=9F7182E3F746AB4EA17801C148F3C604331100E0@IRSMSX101.ger.corp.intel.com \
--to=roy.fan.zhang@intel.com \
--cc=arei.gonglei@huawei.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=jianjay.zhou@huawei.com \
--cc=maxime.coquelin@redhat.com \
--cc=wangxinxin.wang@huawei.com \
--cc=weidong.huang@huawei.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).