From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Sasha Levin <sashal@kernel.org>
Cc: intel-gvt-dev@lists.freedesktop.org, "Monroy,
Rodrigo Axel" <rodrigo.axel.monroy@intel.com>,
"Orrala Contreras, Alfredo" <alfredo.orrala.contreras@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915/gvt: Fix mmap range check
Date: Thu, 17 Jan 2019 15:12:32 +0800 [thread overview]
Message-ID: <20190117071232.GH18272@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <20190116133557.4158F20866@mail.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On 2019.01.16 13:35:56 +0000, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 659643f7d814 drm/i915/gvt/kvmgt: add vfio/mdev support to KVMGT.
>
> The bot has tested the following trees: v4.20.2, v4.19.15, v4.14.93.
>
> v4.20.2: Build OK!
> v4.19.15: Build OK!
> v4.14.93: Build failed! Errors:
> drivers/gpu/drm/i915/gvt/kvmgt.c:836:7: error: implicit declaration of function ???intel_vgpu_in_aperture???; did you mean ???intel_vgpu_create???? [-Werror=implicit-function-declaration]
>
>
> How should we proceed with this patch?
>
I'll prepare a backport version once this one hits linux master.
Thanks.
--
Open Source Technology Center, Intel ltd.
$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2019-01-17 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 5:58 [PATCH] drm/i915/gvt: Fix mmap range check Zhenyu Wang
2019-01-15 10:55 ` Yuan, Hang
[not found] ` <20190116133557.4158F20866@mail.kernel.org>
2019-01-17 7:12 ` Zhenyu Wang [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=20190117071232.GH18272@zhen-hp.sh.intel.com \
--to=zhenyuw@linux.intel.com \
--cc=alfredo.orrala.contreras@intel.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=rodrigo.axel.monroy@intel.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.