From: David Marchand <david.marchand@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev <dev@dpdk.org>, "Xia, Chenbo" <chenbo.xia@intel.com>,
Xiao Wang <xiao.w.wang@intel.com>, dpdk stable <stable@dpdk.org>,
Brandon Lo <blo@iol.unh.edu>
Subject: Re: [dpdk-stable] [PATCH] vdpa/ifc: fix build issue with recent kernels
Date: Fri, 2 Oct 2020 10:33:31 +0200 [thread overview]
Message-ID: <CAJFAV8yW292vUkGFaibudBMqt1uzmTtm4sCnm_e4jfchMiXSDw@mail.gmail.com> (raw)
In-Reply-To: <20201002075400.248206-1-maxime.coquelin@redhat.com>
On Fri, Oct 2, 2020 at 9:54 AM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
>
> VIRTIO_F_IOMMU_PLATFORM is now defined in recent kernel
> headers, causing build issue.
>
> Le's define it in IFC vDPA driver only if wasn't already.
Let's* define it in the* IFC vDPA driver only if it* wasn't already.
>
> Fixes: a3f8150eac6d ("net/ifcvf: add ifcvf vDPA driver")
> Cc: stable@dpdk.org
>
> Reported-by: Brandon Lo <blo@iol.unh.edu>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
> drivers/vdpa/ifc/base/ifcvf.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/vdpa/ifc/base/ifcvf.h b/drivers/vdpa/ifc/base/ifcvf.h
> index a288ce57dc..573a35ffb4 100644
> --- a/drivers/vdpa/ifc/base/ifcvf.h
> +++ b/drivers/vdpa/ifc/base/ifcvf.h
> @@ -13,7 +13,10 @@
> #define IFCVF_SUBSYS_DEVICE_ID 0x001A
>
> #define IFCVF_MAX_QUEUES 1
> +
> +#ifndef VIRTIO_F_IOMMU_PLATFORM
> #define VIRTIO_F_IOMMU_PLATFORM 33
> +#endif
>
> /* Common configuration */
> #define IFCVF_PCI_CAP_COMMON_CFG 1
> --
> 2.26.2
>
Acked-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
next prev parent reply other threads:[~2020-10-02 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 7:54 Maxime Coquelin
2020-10-02 8:33 ` David Marchand [this message]
2020-10-02 16:40 ` David Marchand
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=CAJFAV8yW292vUkGFaibudBMqt1uzmTtm4sCnm_e4jfchMiXSDw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=blo@iol.unh.edu \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.org \
--cc=xiao.w.wang@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).