From: Zhi Wang <zhi.wang.linux@gmail.com>
To: rodrigo.vivi@intel.com, jani.nikula@linux.intel.com,
joonas.lahtinen@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org
Subject: [Intel-gfx] [GVT PULL] gvt-fixes for drm-intel-fixes
Date: Sat, 15 Jan 2022 10:46:20 +0000 [thread overview]
Message-ID: <1f619581-e3da-3899-09ac-f714d954a580@gmail.com> (raw)
Hi folks:
Here is the gvt-fixes pull for drm-intel-fixes. It contains:
- Make DRM_I915_GVT depend on X86 (Siva Mullati)
- Clean kernel doc in gtt.c (Randy Dunlap)
This pull has been tested by: dim apply-pull drm-intel-fixes < this_email.eml
Zhi.
The following changes since commit d46f329a3f6048e04736e86cb13c880645048792:
drm/i915: Increment composite fence seqno (2021-12-27 11:33:40 +0200)
are available in the Git repository at:
https://github.com/intel/gvt-linux.git tags/gvt-fixes-2022-01-13
for you to fetch changes up to d72d69abfdb6e0375981cfdda8eb45143f12c77d:
drm/i915/gvt: Make DRM_I915_GVT depend on X86 (2022-01-13 18:13:12 +0000)
----------------------------------------------------------------
gvt-fixes-2022-01-13
- Make DRM_I915_GVT depend on X86 (Siva Mullati)
- Clean kernel doc in gtt.c (Randy Dunlap)
----------------------------------------------------------------
Randy Dunlap (1):
drm/i915/gvt: clean up kernel-doc in gtt.c
Siva Mullati (1):
drm/i915/gvt: Make DRM_I915_GVT depend on X86
drivers/gpu/drm/i915/Kconfig | 1 +
drivers/gpu/drm/i915/gvt/gtt.c | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
next reply other threads:[~2022-01-15 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 10:46 Zhi Wang [this message]
2022-02-09 15:36 ` [Intel-gfx] [GVT PULL] gvt-fixes for drm-intel-fixes Wang, Zhi A
2022-02-10 8:51 ` Jani Nikula
2022-02-10 10:14 ` Wang, Zhi A
2022-02-10 11:01 ` Tvrtko Ursulin
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=1f619581-e3da-3899-09ac-f714d954a580@gmail.com \
--to=zhi.wang.linux@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@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