From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PULL] gvt-next
Date: Thu, 17 Nov 2022 14:41:06 +0800 [thread overview]
Message-ID: <20221117064106.GT30028@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <6d9f565acb5bd57ee2df79fc5a9cf802724a3333.camel@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3018 bytes --]
On 2022.11.17 03:37:17 +0000, Vivi, Rodrigo wrote:
> On Thu, 2022-11-17 at 11:02 +0800, Zhenyu Wang wrote:
> > 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.
> > > >
>
> Based on what I could verify the commiter signature is really not
> there. It looks like you later forced a rebase and while
> rebasing you forgot to re-sign everything.
>
Hi, pls re-pull this one.
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-17
for you to fetch changes up to 04ec334e1a0381c3305da4d277cef9250769ca43:
drm/i915/gvt: Remove the unused function get_pt_type() (2022-11-17 14:07:09 +0800)
----------------------------------------------------------------
gvt-next-2022-11-17
- kernel doc fixes
- remove vgpu->released sanity check
- small clean up
----------------------------------------------------------------
Colin Ian King (1):
drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported"
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 --]
next prev parent reply other threads:[~2022-11-17 6:41 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
2022-11-17 3:37 ` Vivi, Rodrigo
2022-11-17 5:28 ` Zhenyu Wang
2022-11-17 6:41 ` Zhenyu Wang [this message]
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=20221117064106.GT30028@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