All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>,
	"Lv,  Zhiyuan" <zhiyuan.lv@intel.com>
Subject: Re: [Intel-gfx] [PULL] gvt-next-fixes
Date: Thu, 23 Feb 2023 14:11:28 +0200	[thread overview]
Message-ID: <87v8js37kf.fsf@intel.com> (raw)
In-Reply-To: <Y/co4cy10KM1/2uX@debian-scheme>

On Thu, 23 Feb 2023, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> Hi,
>
> This is what are on gvt tree now for next kernel, including fixes for
> gvt debugfs, one kconfig symbol fix for menu presentation and misc
> typo fixes. Please check details below. This is generated against current
> drm-intel-next-fixes.

Thanks, pulled to drm-intel-next-fixes, and pushed out.

BR,
Jani.


>
> Thanks!
> --
> The following changes since commit 8038510b1fe443ffbc0e356db5f47cbb8678a594:
>
>   drm/i915: Fix system suspend without fbdev being initialized (2023-02-15 17:33:07 +0200)
>
> are available in the Git repository at:
>
>   https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2023-02-23
>
> for you to fetch changes up to 0b93efca3659f6d55ed31cff6722dca5f6e4d6e2:
>
>   drm/i915: move a Kconfig symbol to unbreak the menu presentation (2023-02-23 13:46:39 +0800)
>
> ----------------------------------------------------------------
> gvt-next-fixes-2023-02-23
>
> - use debugfs attribute for gvt debugfs entries (Deepak R Varma)
> - fix memory leak in vgpu destroy for debugfs_lookup() then remove (Greg KH)
> - fix DRM_I915_GVT kconfig symbol to unbreak menu presentation (Randy Dunlap)
> - fix typos (Deepak R Varma, Colin Ian King)
>
> ----------------------------------------------------------------
> Colin Ian King (1):
>       i915/gvt: Fix spelling mistake "vender" -> "vendor"
>
> Deepak R Varma (2):
>       drm/i915/gvt: Avoid full proxy f_ops for debugfs attributes
>       drm/i915/gvt: Remove extra semicolon
>
> Greg Kroah-Hartman (1):
>       i915: fix memory leak with using debugfs_lookup()
>
> Randy Dunlap (1):
>       drm/i915: move a Kconfig symbol to unbreak the menu presentation
>
>  drivers/gpu/drm/i915/Kconfig        |  6 +++---
>  drivers/gpu/drm/i915/gvt/debugfs.c  | 16 ++++++++--------
>  drivers/gpu/drm/i915/gvt/firmware.c |  2 +-
>  drivers/gpu/drm/i915/gvt/kvmgt.c    |  2 +-
>  drivers/gpu/drm/i915/gvt/vgpu.c     |  2 +-
>  5 files changed, 14 insertions(+), 14 deletions(-)

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-02-23 12:13 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23  8:50 [Intel-gfx] [PULL] gvt-next-fixes Zhenyu Wang
2023-02-23 12:11 ` Jani Nikula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-28  7:47 Zhenyu Wang
2021-04-29  8:51 Zhenyu Wang
2021-04-29 11:12 ` Jani Nikula
2021-04-21  9:45 Zhenyu Wang
2021-04-21 10:51 ` Jani Nikula
2021-02-22  8:34 Zhenyu Wang
2021-02-23 14:42 ` Rodrigo Vivi
2020-12-25  2:20 Zhenyu Wang
2021-01-05  7:54 ` Zhenyu Wang
2021-01-05  8:36   ` Jani Nikula
2021-01-05 20:44     ` Rodrigo Vivi
2020-08-05  8:02 Zhenyu Wang
2020-08-06 15:17 ` Jani Nikula
2020-05-28  3:35 Zhenyu Wang
2020-06-02 14:04 ` Joonas Lahtinen
2020-03-31  7:00 Zhenyu Wang
2020-03-31 16:26 ` Rodrigo Vivi
2020-04-03  3:05   ` Zhenyu Wang
2020-04-03 17:50     ` Rodrigo Vivi
2020-04-07  8:02       ` Zhenyu Wang
2020-04-07 13:35         ` Rodrigo Vivi
2020-04-07 13:53           ` Jani Nikula
2020-04-07 23:36             ` Zhenyu Wang
2019-12-02  5:17 Zhenyu Wang
2019-12-02  5:17 ` Zhenyu Wang
2019-12-05  6:11   ` Zhenyu Wang
2019-12-05  8:14     ` Joonas Lahtinen
2019-12-05  8:49       ` Zhenyu Wang
2019-11-12  6:20 Zhenyu Wang
2019-11-12  6:20 ` Zhenyu Wang
2019-11-20 11:25   ` Joonas Lahtinen
2019-11-20 11:25     ` Joonas Lahtinen

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=87v8js37kf.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=tvrtko.ursulin@linux.intel.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhiyuan.lv@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 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.