All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Pandiyan Dhinakaran <dhinakaran.pandiyan@intel.com>
Subject: Re: [PATCH v2 1/3] Documentation/i915: remove sphinx conversion artefact
Date: Thu, 10 Aug 2017 19:13:50 +0300	[thread overview]
Message-ID: <87efsjs8n5.fsf@intel.com> (raw)
In-Reply-To: <CABVU7+uL5ym-C_c3+iH87g95wpUYABLf=KAE2GtTUBFM+1Jv_w@mail.gmail.com>

On Thu, 10 Aug 2017, Rodrigo Vivi <rodrigo.vivi@gmail.com> wrote:
> On Thu, Aug 10, 2017 at 5:29 AM, Jani Nikula <jani.nikula@intel.com> wrote:
>> Remove old warning about docproc directive that's not supported in the
>> Sphinx toolchain.
>
> I got confused... the warning is not supported by sphinx or docproc?

There used to be a docproc directive !C to ensure all (documented?)
functions in the specified file were used in the docbook build. The
docbook -> sphinx conversion retained those as commented out warnings in
the rst source. I don't think we'll have similar functionality in sphinx
anytime soon. So just nuke it.

BR,
Jani.

>
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>>  Documentation/gpu/i915.rst | 2 --
>>  1 file changed, 2 deletions(-)
>>
>> diff --git a/Documentation/gpu/i915.rst b/Documentation/gpu/i915.rst
>> index 46875c2bcc31..32c32b89e2e5 100644
>> --- a/Documentation/gpu/i915.rst
>> +++ b/Documentation/gpu/i915.rst
>> @@ -480,5 +480,3 @@ specific details than found in the more high-level sections.
>>
>>  .. kernel-doc:: drivers/gpu/drm/i915/i915_perf.c
>>     :internal:
>> -
>> -.. WARNING: DOCPROC directive not supported: !Cdrivers/gpu/drm/i915/i915_irq.c
>> --
>> 2.11.0
>>

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-08-10 16:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10 12:29 [PATCH v2 0/3] drm/i915: add register macro definition style guide Jani Nikula
2017-08-10 12:29 ` [PATCH v2 1/3] Documentation/i915: remove sphinx conversion artefact Jani Nikula
2017-08-10 15:19   ` Rodrigo Vivi
2017-08-10 16:13     ` Jani Nikula [this message]
2017-08-10 19:31       ` Rodrigo Vivi
2017-08-10 12:29 ` [PATCH v2 2/3] drm/i915: enum i915_power_well_id is not proper kernel-doc Jani Nikula
2017-08-10 15:17   ` Rodrigo Vivi
2017-08-10 12:29 ` [PATCH v2 3/3] drm/i915: add register macro definition style guide Jani Nikula
2017-08-10 12:55 ` ✗ Fi.CI.BAT: failure for drm/i915: add register macro definition style guide (rev2) Patchwork
2017-08-10 20:11   ` Jani Nikula

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=87efsjs8n5.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=dhinakaran.pandiyan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.