From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
"Yuan, Hang" <hang.yuan@intel.com>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
"Vetter, Daniel" <daniel.vetter@intel.com>,
intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [PULL] gvt-next for 4.19
Date: Mon, 16 Jul 2018 23:07:35 -0700 [thread overview]
Message-ID: <20180717060735.GA32201@intel.com> (raw)
In-Reply-To: <20180717045837.GP1267@zhen-hp.sh.intel.com>
On Tue, Jul 17, 2018 at 12:58:37PM +0800, Zhenyu Wang wrote:
>
> Hi,
>
> Left fixes for all W=1 warnings, I think better to send
> to catch up last train for 4.19, mostly kernel doc comments
> fixes with a trivial refactor.
I was going to pull it and by pass dim...
The changes on the patches themselves is something simple enough that I would
ack myself, although in one of patches if we had review I'm sure
that would become 2 patches....
So at this point I'm not sure if I should bypass dim or request
another eyes... so I'm just, at least, holding until tomorrow...
>
> Thanks
> --
> The following changes since commit 279ce5d117078ee8ea40c40199399889981fd808:
>
> drm/i915/gvt: declare gvt as i915's soft dependency (2018-07-10 11:13:11 +0800)
>
> are available in the Git repository at:
>
> https://github.com/intel/gvt-linux.git tags/gvt-next-2018-07-17
>
> for you to fetch changes up to 3e494c2eb417715cdfed66827a5752e41de748c3:
>
> drm/i915/gvt: Fix W=1 warnings (2018-07-16 13:28:47 +0800)
>
> ----------------------------------------------------------------
> gvt-next-2018-07-17
>
> - Fix all left W=1 warnings
>
> ----------------------------------------------------------------
> Zhenyu Wang (2):
> drm/i915/gvt: make dma map/unmap kvmgt functions as static
> drm/i915/gvt: Fix W=1 warnings
>
> drivers/gpu/drm/i915/gvt/cfg_space.c | 12 ++++++++++++
> drivers/gpu/drm/i915/gvt/display.c | 1 +
> drivers/gpu/drm/i915/gvt/edid.c | 9 +++++++++
> drivers/gpu/drm/i915/gvt/gtt.c | 9 ++++++---
> drivers/gpu/drm/i915/gvt/gvt.c | 3 +--
> drivers/gpu/drm/i915/gvt/handlers.c | 1 +
> drivers/gpu/drm/i915/gvt/kvmgt.c | 4 ++--
> drivers/gpu/drm/i915/gvt/mmio.c | 3 ++-
> drivers/gpu/drm/i915/gvt/mmio_context.c | 13 -------------
> drivers/gpu/drm/i915/gvt/opregion.c | 1 -
> drivers/gpu/drm/i915/gvt/page_track.c | 2 ++
> drivers/gpu/drm/i915/gvt/reg.h | 9 +++++++++
> drivers/gpu/drm/i915/gvt/scheduler.c | 4 +++-
> 13 files changed, 48 insertions(+), 23 deletions(-)
>
>
> --
> Open Source Technology Center, Intel ltd.
>
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-17 6:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 4:58 [PULL] gvt-next for 4.19 Zhenyu Wang
2018-07-17 6:07 ` Rodrigo Vivi [this message]
2018-07-17 6:06 ` Zhenyu Wang
-- strict thread matches above, loose matches on Subject: below --
2018-07-11 2:33 Zhenyu Wang
2018-07-11 7:45 ` Chris Wilson
2018-07-11 7:47 ` Zhenyu Wang
2018-07-12 7:33 ` 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=20180717060735.GA32201@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=daniel.vetter@intel.com \
--cc=hang.yuan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).