From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Luca Boccassi <bluca@debian.org>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 16.11 2/2] vfio: fix build
Date: Fri, 23 Nov 2018 09:29:53 +0000 [thread overview]
Message-ID: <ae997430-15c8-8e60-84b7-5d4886189ef0@intel.com> (raw)
In-Reply-To: <20181121164802.8186-2-bluca@debian.org>
On 21-Nov-18 4:48 PM, Luca Boccassi wrote:
> From: Anatoly Burakov <anatoly.burakov@intel.com>
>
> [ backported from upstream commit 9fa5993f103712d10be0f0b111a3a9afc92cd9e6 ]
>
> Some compilers require definition of vfio_iommu_spapr_tce_ddw_info
> before its use in vfio_iommu_spapr_tce_info, so move tce_info
> definition below tce_ddw_info.
>
> Fixes: 468f42cc2645 ("vfio: fix build on old kernel")
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
The patchset can probably be squashed into one patch, since the latter
is fix for the former.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-11-23 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 16:48 [dpdk-stable] [PATCH 16.11 1/2] vfio: fix build on old kernel Luca Boccassi
2018-11-21 16:48 ` [dpdk-stable] [PATCH 16.11 2/2] vfio: fix build Luca Boccassi
2018-11-23 9:29 ` Burakov, Anatoly [this message]
2018-11-23 9:26 ` [dpdk-stable] [PATCH 16.11 1/2] vfio: fix build on old kernel Burakov, Anatoly
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=ae997430-15c8-8e60-84b7-5d4886189ef0@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bluca@debian.org \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).