From: Julian Stecklina <julian.stecklina@cyberus-technology.de>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: zhiyuan.lv@intel.com, intel-gvt-dev@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
hang.yuan@intel.com
Subject: Re: [PATCH 1/3] drm/i915/gvt: fix file paths in documentation
Date: Wed, 08 Jan 2020 10:24:22 +0200 [thread overview]
Message-ID: <ab56cd76c4a4c1266ca35df1645d05bfeae58e25.camel@cyberus-technology.de> (raw)
In-Reply-To: <20200107020637.GA5894@zhen-hp.sh.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1816 bytes --]
On Tue, 2020-01-07 at 10:06 +0800, Zhenyu Wang wrote:
> On 2020.01.06 16:06:20 +0200, Julian Stecklina wrote:
> > The documentation had some stale paths to i915 graphics virtualization
> > code. Fix them to point to existing files.
> >
> > Cc: Zhenyu Wang <zhenyuw@linux.intel.com>
> > Cc: zhiyuan.lv@intel.com
> > Cc: hang.yuan@intel.com
> >
> > Signed-off-by: Julian Stecklina <julian.stecklina@cyberus-technology.de>
> > ---
> > Documentation/gpu/i915.rst | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/Documentation/gpu/i915.rst b/Documentation/gpu/i915.rst
> > index e539c42a3e78..d644683c5249 100644
> > --- a/Documentation/gpu/i915.rst
> > +++ b/Documentation/gpu/i915.rst
> > @@ -43,19 +43,19 @@ Interrupt Handling
> > Intel GVT-g Guest Support(vGPU)
> > -------------------------------
> >
> > -.. kernel-doc:: drivers/gpu/drm/i915/i915_vgpu.c
> > +.. kernel-doc:: drivers/gpu/drm/i915/gvt/vgpu.c
> > :doc: Intel GVT-g guest support
> >
> > -.. kernel-doc:: drivers/gpu/drm/i915/i915_vgpu.c
> > +.. kernel-doc:: drivers/gpu/drm/i915/gvt/vgpu.c
> > :internal:
> >
> > Intel GVT-g Host Support(vGPU device model)
> > -------------------------------------------
> >
> > -.. kernel-doc:: drivers/gpu/drm/i915/intel_gvt.c
> > +.. kernel-doc:: drivers/gpu/drm/i915/gvt/gvt.c
> > :doc: Intel GVT-g host support
> >
> > -.. kernel-doc:: drivers/gpu/drm/i915/intel_gvt.c
> > +.. kernel-doc:: drivers/gpu/drm/i915/gvt/gvt.c
> > :internal:
> >
>
> The i915_vgpu.c and intel_gvt.c are still there for guest
> and host part of i915 interface with gvt. We still need them
> in doc. The files in gvt/ directory are gvt device model internals.
Thanks for clarifying. I'll drop the patch.
Julian
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2020-01-08 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 14:06 [PATCH 1/3] drm/i915/gvt: fix file paths in documentation Julian Stecklina
2020-01-06 14:06 ` [PATCH 2/3] drm/i915/gvt: make gvt oblivious of kvmgt data structures Julian Stecklina
2020-01-08 10:24 ` Jani Nikula
2020-01-08 16:08 ` Julian Stecklina
2020-01-09 9:29 ` Jani Nikula
2020-01-06 14:06 ` [PATCH 3/3] drm/i915/gvt: remove unused vblank_done completion Julian Stecklina
2020-01-07 2:06 ` [PATCH 1/3] drm/i915/gvt: fix file paths in documentation Zhenyu Wang
2020-01-08 8:24 ` Julian Stecklina [this message]
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=ab56cd76c4a4c1266ca35df1645d05bfeae58e25.camel@cyberus-technology.de \
--to=julian.stecklina@cyberus-technology.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=hang.yuan@intel.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--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).