From: Thomas Monjalon <thomas@monjalon.net>
To: Jeff Guo <jia.guo@intel.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
anatoly.burakov@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] vfio: fix build issue
Date: Tue, 16 Oct 2018 14:55:58 +0200 [thread overview]
Message-ID: <13173016.DHzOh1Wy4B@xps> (raw)
In-Reply-To: <10ce3595-ea26-59a5-e4ab-d3780edde2f3@intel.com>
16/10/2018 14:52, Ferruh Yigit:
> On 10/16/2018 12:42 PM, Jeff Guo wrote:
> > Since the older kernel version do not implement the device request
> > interface for vfio, so when build on the kernel < v4.0.0, which is
> > the version begin to add the device request interface, it will
> > throw the error to show “VFIO_PCI_REQ_IRQ_INDEX” is undeclared.
> > This patch aim to fix this compile issue by add the macro
> > “HAVE_VFIO_DEV_REQ_INTERFACE” after checking the kernel version.
> >
> > Signed-off-by: Jeff Guo <jia.guo@intel.com>
>
> Fixes: 0eb8a1c4c786 ("vfio: add request notifier interrupt")
> Fixes: c115fd000c32 ("vfio: handle hotplug request notifier")
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Series applies, thanks
prev parent reply other threads:[~2018-10-16 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 11:42 Jeff Guo
2018-10-16 12:52 ` Ferruh Yigit
2018-10-16 12:55 ` 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=13173016.DHzOh1Wy4B@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jia.guo@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).