From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Jani Nikula <jani.nikula@intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>,
zhi.wang.linux@gmail.com
Subject: [PULL] gvt-fixes
Date: Wed, 31 Jan 2024 17:38:51 +0800 [thread overview]
Message-ID: <ZboVK03/Eb/jt7wf@debian-scheme> (raw)
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
Hi, Joonas
Here is another gvt-fixes pull which contains fixes on doc link and
one uninitialized variable in warning message, also update about Zhi's
new mail address in MAINTAINERS.
Thanks.
---
The following changes since commit f9f031dd21a7ce13a13862fa5281d32e1029c70f:
drm/i915/psr: Only allow PSR in LPSP mode on HSW non-ULT (2024-01-25 10:44:13 +0200)
are available in the Git repository at:
https://github.com/intel/gvt-linux tags/gvt-fixes-2024-01-31
for you to fetch changes up to 88569fa2c3bc83d77a96580da94dd35edee0f893:
MAINTAINERS: Update Zhi Wang's email address (2024-01-31 17:19:15 +0800)
----------------------------------------------------------------
gvt-fixes-2024-01-31
- Fix broken gvt doc link (Zhenyu)
- Fix one uninitialized variable bug in warning (Dan)
- Update Zhi's new email address in MAINTAINERS file. (Zhi)
----------------------------------------------------------------
Dan Carpenter (1):
drm/i915/gvt: Fix uninitialized variable in handle_mmio()
Zhenyu Wang (1):
drm/i915: Replace dead 01.org link
Zhi Wang (1):
MAINTAINERS: Update Zhi Wang's email address
MAINTAINERS | 4 ++--
drivers/gpu/drm/i915/Kconfig | 2 +-
drivers/gpu/drm/i915/gvt/handlers.c | 3 +--
drivers/gpu/drm/i915/intel_gvt.c | 2 +-
4 files changed, 5 insertions(+), 6 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2024-01-31 9:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 9:38 Zhenyu Wang [this message]
2024-02-01 14:44 ` [PULL] gvt-fixes Joonas Lahtinen
2024-02-05 3:21 ` Zhenyu Wang
-- strict thread matches above, loose matches on Subject: below --
2019-11-22 3:33 Zhenyu Wang
2019-11-12 6:18 Zhenyu Wang
2019-11-12 20:36 ` Vivi, Rodrigo
2019-08-13 9:58 Zhenyu Wang
2019-08-13 13:41 ` Jani Nikula
2019-07-23 9:29 Zhenyu Wang
2019-07-29 3:33 ` Zhenyu Wang
2019-07-29 11:05 ` Jani Nikula
2019-07-30 7:00 ` Zhenyu Wang
2019-07-30 8:33 ` Jani Nikula
2019-06-19 6:22 Zhenyu Wang
2019-06-19 7:56 ` Jani Nikula
2019-06-05 8:49 Zhenyu Wang
2019-06-06 12:04 ` Joonas Lahtinen
2019-05-29 9:06 Zhenyu Wang
2019-05-29 12:07 ` Joonas Lahtinen
2019-05-30 3:41 ` Zhenyu Wang
2019-05-31 8:16 ` Joonas Lahtinen
2019-05-21 6:24 Zhenyu Wang
2019-05-21 12:35 ` Joonas Lahtinen
2019-04-11 6:49 Zhenyu Wang
2019-04-11 16:48 ` Rodrigo Vivi
2019-04-02 9:40 Zhenyu Wang
2019-04-04 0:12 ` Rodrigo Vivi
2019-04-04 0:32 ` Zhenyu Wang
2019-04-04 1:03 ` Rodrigo Vivi
2019-04-04 0:39 ` Zhenyu Wang
2019-03-21 3:50 Zhenyu Wang
2019-03-21 20:03 ` Rodrigo Vivi
2019-01-24 5:48 Zhenyu Wang
2019-01-31 9:45 ` Jani Nikula
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=ZboVK03/Eb/jt7wf@debian-scheme \
--to=zhenyuw@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=zhi.wang.linux@gmail.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