public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PULL] gvt-next
Date: Thu, 17 Nov 2022 11:02:15 +0800	[thread overview]
Message-ID: <20221117030215.GR30028@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <Y3OyGyJLhL7k8EV+@intel.com>

[-- Attachment #1: Type: text/plain, Size: 3229 bytes --]

On 2022.11.15 10:36:59 -0500, Rodrigo Vivi wrote:
> On Fri, Nov 11, 2022 at 04:59:03PM +0800, Zhenyu Wang wrote:
> > Hi,
> > 
> > Here's current accumulated changes in gvt-next. Sorry that I delayed
> > to refresh them on time for upstream...It contains mostly kernel doc,
> > typo fixes and small code cleanups, as details below.
> > 
> > btw, one gvt change for next https://patchwork.freedesktop.org/patch/511118/
> > is still pending, I need a backmerge from linus tree e.g with recent vfio/mdev
> > consolidate change with gvt and Jason's fix for destroy device, to apply Zhi's
> > change cleanly. Pls help on that.
> > 
> > Thanks!
> > ---
> > The following changes since commit a6ebd538364b1e9e6048faaafbc0188172ed50c3:
> > 
> >   drm/i915/sdvo: Fix debug print (2022-10-28 14:46:21 +0300)
> > 
> > are available in the Git repository at:
> > 
> >   https://github.com/intel/gvt-linux.git tags/gvt-next-2022-11-11
> > 
> > for you to fetch changes up to 50468ca2e2e1ce882f060a8c263f678affe112db:
> > 
> >   drm/i915/gvt: Remove the unused function get_pt_type() (2022-11-08 15:34:06 +0800)
> > 
> > ----------------------------------------------------------------
> > gvt-next-2022-11-11
> > 
> > - kernel doc fixes
> > - remove vgpu->released sanity check
> > - small clean up
> > 
> > ----------------------------------------------------------------
> > Colin Ian King (1):
> >       drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported"
> 
> dim: d7e4e9579f01 ("drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported""): committer Signed-off-by missing.
> 
> could you please fix this before we can merge this pr?
>

That should still be .mailmap issue for Colin's email...
But could we improve our dim script to grep mailmap in that case? So if s-o-b mail is valid
in mailmap, we should still allow it, right?

> > 
> > Jiapeng Chong (4):
> >       drm/i915/gvt: Fix kernel-doc
> >       drm/i915/gvt: Fix kernel-doc
> >       drm/i915/gvt: Fix kernel-doc
> >       drm/i915/gvt: Remove the unused function get_pt_type()
> > 
> > Julia Lawall (1):
> >       drm/i915/gvt: fix typo in comment
> > 
> > Mauro Carvalho Chehab (1):
> >       drm/i915: gvt: fix kernel-doc trivial warnings
> > 
> > Paulo Miguel Almeida (1):
> >       i915/gvt: remove hardcoded value on crc32_start calculation
> > 
> > Zhi Wang (1):
> >       drm/i915/gvt: remove the vgpu->released and its sanity check
> > 
> > wangjianli (1):
> >       drm/i915: fix repeated words in comments
> > 
> >  drivers/gpu/drm/i915/gvt/aperture_gm.c  | 4 ++--
> >  drivers/gpu/drm/i915/gvt/cfg_space.c    | 2 +-
> >  drivers/gpu/drm/i915/gvt/dmabuf.h       | 2 +-
> >  drivers/gpu/drm/i915/gvt/firmware.c     | 2 +-
> >  drivers/gpu/drm/i915/gvt/gtt.c          | 9 ++-------
> >  drivers/gpu/drm/i915/gvt/gvt.h          | 2 --
> >  drivers/gpu/drm/i915/gvt/handlers.c     | 4 ++--
> >  drivers/gpu/drm/i915/gvt/kvmgt.c        | 4 ----
> >  drivers/gpu/drm/i915/gvt/mmio_context.c | 2 +-
> >  drivers/gpu/drm/i915/gvt/page_track.c   | 2 +-
> >  drivers/gpu/drm/i915/gvt/vgpu.c         | 6 +++---
> >  11 files changed, 14 insertions(+), 25 deletions(-)
> 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-11-17  3:03 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2022-04-26  7:58 Wang, Zhi A
2022-04-26  8:37 ` Jani Nikula
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-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
2020-07-20  8:05 Zhenyu Wang
2020-07-21 11:04 ` Joonas Lahtinen
2020-07-22  0:42   ` Zhenyu Wang
2020-07-27 16:39     ` Vivi, Rodrigo
2020-07-28  3:18       ` Zhenyu Wang
2020-05-12  9:40 Zhenyu Wang
2020-05-14 16:04 ` Joonas Lahtinen
2020-04-22  5:12 Zhenyu Wang
2020-04-26  2:46 ` Zhenyu Wang
2020-04-30 12:38   ` Joonas Lahtinen
2020-03-10  8:19 Zhenyu Wang
2020-03-10 22:50 ` Rodrigo Vivi
2020-02-26 10:38 Zhenyu Wang
2020-02-26 11:58 ` Jani Nikula
2020-02-27  9:31   ` Zhenyu Wang
2020-02-26 23:10 ` Rodrigo Vivi

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=20221117030215.GR30028@zhen-hp.sh.intel.com \
    --to=zhenyuw@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox