From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Oscar Mateo <oscar.mateo@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v6 1/2] drm/i915: Move a bunch of workaround-related code to its own file
Date: Tue, 27 Feb 2018 12:06:01 +0200 [thread overview]
Message-ID: <87o9kawxva.fsf@intel.com> (raw)
In-Reply-To: <151968721935.16206.16723734216616437001@mail.alporthouse.com>
On Mon, 26 Feb 2018, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Oscar Mateo (2018-02-26 23:01:50)
>> diff --git a/Documentation/gpu/i915.rst b/Documentation/gpu/i915.rst
>> index 41dc881..e41678f 100644
>> --- a/Documentation/gpu/i915.rst
>> +++ b/Documentation/gpu/i915.rst
>> @@ -58,6 +58,12 @@ Intel GVT-g Host Support(vGPU device model)
>> .. kernel-doc:: drivers/gpu/drm/i915/intel_gvt.c
>> :internal:
>>
>> +Workarounds
>> +-----------
>> +
>> +.. kernel-doc:: drivers/gpu/drm/i915/intel_workarounds.c
>> + :doc: Hardware workarounds
>> +
>
> If the kerneldoc insists on having the overview + index being in a
> separate namespace to the code, could we at least have a symlink to
> drivers/gpu/drm/i915/i915.rst so that we don't have to keep hunting for
> it?
$ find -type l | wc -l
34
and none of them under drivers. I'm not sure I'd want to stick my neck
out in this department...
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-02-27 10:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 22:03 [PATCH v5 1/2] drm/i915: Move a bunch of workaround-related code to its own file Oscar Mateo
2018-02-23 22:03 ` [PATCH v5 2/2] drm/i915: Split out functions for different kinds of workarounds Oscar Mateo
2018-02-23 22:08 ` ✗ Fi.CI.SPARSE: warning for series starting with [v5,1/2] drm/i915: Move a bunch of workaround-related code to its own file Patchwork
2018-02-23 22:25 ` ✗ Fi.CI.BAT: " Patchwork
2018-02-26 10:16 ` [PATCH v5 1/2] " Jani Nikula
2018-02-26 23:01 ` [PATCH v6 " Oscar Mateo
2018-02-26 23:20 ` Chris Wilson
2018-02-27 10:06 ` Jani Nikula [this message]
2018-02-26 23:36 ` ✗ Fi.CI.SPARSE: warning for series starting with [v6,1/2] drm/i915: Move a bunch of workaround-related code to its own file (rev2) Patchwork
2018-02-26 23:49 ` ✓ Fi.CI.BAT: success " Patchwork
2018-02-27 2:54 ` ✓ Fi.CI.IGT: " Patchwork
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=87o9kawxva.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=oscar.mateo@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).