All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] drm/doc: Drop :c:func: markup
Date: Thu, 5 Dec 2019 17:05:37 +0100	[thread overview]
Message-ID: <20191205160537.GC1914185@ulmo> (raw)
In-Reply-To: <20191204101933.861169-1-daniel.vetter@ffwll.ch>


[-- Attachment #1.1: Type: text/plain, Size: 822 bytes --]

On Wed, Dec 04, 2019 at 11:19:33AM +0100, Daniel Vetter wrote:
> Kernel sphinx has learned how to do that in
> 
> commit d74b0d31dddeac2b44c715588d53d9a1e5b1158e
> Author: Jonathan Corbet <corbet@lwn.net>
> Date:   Thu Apr 25 07:55:07 2019 -0600
> 
>     Docs: An initial automarkup extension for sphinx
> 
> Unfortunately it hasn't learned that yet for structures, so we're
> stuck with the :c:type: noise for now still.
> 
> Cc:  Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
>  Documentation/gpu/drm-internals.rst |  4 +-
>  Documentation/gpu/drm-kms.rst       |  7 ++-
>  Documentation/gpu/drm-mm.rst        | 68 +++++++++++++----------------
>  3 files changed, 36 insertions(+), 43 deletions(-)

Reviewed-by: Thierry Reding <treding@nvidia.com>

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-12-05 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 10:19 [PATCH] drm/doc: Drop :c:func: markup Daniel Vetter
2019-12-05 16:05 ` Thierry Reding [this message]
2019-12-10 10:33   ` Daniel Vetter
2019-12-10 12:15     ` Thierry Reding
2019-12-10 14:17     ` Jonathan Corbet

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=20191205160537.GC1914185@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=corbet@lwn.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    /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.