From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Wang, Zhi A" <zhi.a.wang@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>, Christoph Hellwig <hch@lst.de>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] [PULL] gvt-next
Date: Tue, 26 Apr 2022 11:37:34 +0300 [thread overview]
Message-ID: <87zgk8tf3l.fsf@intel.com> (raw)
In-Reply-To: <c5cf6773-e7a2-8ba8-4cde-0bb14007bc6b@intel.com>
On Tue, 26 Apr 2022, "Wang, Zhi A" <zhi.a.wang@intel.com> wrote:
> Hi folks:
>
> Here is the pull of gvt-next which fixs the compilation error when i915 debug
> is open after the GVT-g refactor patches.
>
> Thanks so much for the efforts.
Pulled, thanks.
BR,
Jani.
>
> Thanks,
> Zhi.
>
> The following changes since commit 2917f53113be3b7a0f374e02cebe6d6b749366b5:
>
> vfio/mdev: Remove mdev drvdata (2022-04-21 07:36:56 -0400)
>
> are available in the Git repository at:
>
> https://github.com/intel/gvt-linux tags/gvt-next-2022-04-26
>
> for you to fetch changes up to 2da299cee780ea797b3f72558687868072cf5eb5:
>
> drm/i915/gvt: Add missing export of symbols. (2022-04-25 18:03:04 -0400)
>
> ----------------------------------------------------------------
> gvt-next-2022-04-26
>
> - Add two missing exports of symbols when i915 debug is enabled.
>
> ----------------------------------------------------------------
> Zhi Wang (1):
> drm/i915/gvt: Add missing export of symbols.
>
> drivers/gpu/drm/i915/intel_gvt.c | 2 ++
> 1 file changed, 2 insertions(+)
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-04-26 8:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 7:58 [Intel-gfx] [PULL] gvt-next Wang, Zhi A
2022-04-26 8:37 ` Jani Nikula [this message]
2022-04-26 8:38 ` Wang, Zhi A
2022-04-26 8:42 ` Wang, Zhi A
2022-04-26 11:52 ` Jason Gunthorpe
2022-04-28 21:35 ` Alex Williamson
2022-04-28 21:48 ` Alex Williamson
2022-04-26 15:53 ` Jason Gunthorpe
2022-04-26 16:58 ` Wang, Zhi A
2022-04-26 19:19 ` Robert Beckett
2022-04-26 15:56 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for gvt-next (rev2) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-11-11 8:59 [Intel-gfx] [PULL] gvt-next Zhenyu Wang
2022-11-15 15:36 ` Rodrigo Vivi
2022-11-17 3:02 ` Zhenyu Wang
2022-11-17 3:37 ` Vivi, Rodrigo
2022-11-17 5:28 ` Zhenyu Wang
2022-11-17 6:41 ` Zhenyu Wang
2022-11-17 13:49 ` Rodrigo Vivi
2022-04-20 8:04 Wang, Zhi A
2022-04-20 12:13 ` Jason Gunthorpe
2022-04-20 14:41 ` Wang, Zhi A
2022-04-20 15:02 ` Jason Gunthorpe
2022-04-20 16:13 ` Wang, Zhi A
2021-03-16 7:43 Zhenyu Wang
2021-03-16 11:52 ` Jani Nikula
2020-11-23 9:05 Zhenyu Wang
2020-11-23 9:32 ` Joonas Lahtinen
2020-11-24 3:13 ` Zhenyu Wang
2020-11-24 9:48 ` Jani Nikula
2020-11-27 13:26 ` Joonas Lahtinen
2020-09-10 5:37 Zhenyu Wang
2020-09-11 23:58 ` Rodrigo Vivi
2020-09-14 2:34 ` Zhenyu Wang
2020-09-14 18:39 ` Vivi, Rodrigo
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=87zgk8tf3l.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=alex.williamson@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jgg@nvidia.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=zhi.a.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