All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Robert Bragg <robert@sixbynine.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/perf: More documentation hooked to	i915.rst
Date: Mon, 12 Dec 2016 12:00:26 +0200	[thread overview]
Message-ID: <878trlv551.fsf@intel.com> (raw)
In-Reply-To: <20161212073404.n5qezxocz5w5ixjp@phenom.ffwll.local>

On Mon, 12 Dec 2016, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Fri, Dec 09, 2016 at 12:41:08PM +0000, Robert Bragg wrote:
>> As a bit of an asside; last year for another project of mine I once
>> wrote an experimental tool for extracting gtk-doc comments from code
>> to using the python clang bindings:
>> https://github.com/rib/clib/blob/master/site/rst-from-c.py
>> 
>> It's crossed my mind to play around with being able to extract
>> kernel-doc with clang along similar lines which could potentially
>> track more type information so the docs could support more than just
>> .. c:function and .. c:type, such as c:macro and c:member and could
>> better handle things like function pointers as members of structs.
>> Maybe it's an idea worth considering.
>
> Talk to Jani, he has it implemented already somewhere. But kernel-doc is a
> horrible, and we have about 50k existing comments that all need to still
> parse, so it's really tricky to move forward.

Yeah, I admit to having a little side project to use python-clang to
extract documentation comments directly into Sphinx.

But I've pretty much decided I'm not going to pursue making it a
replacement for kernel-doc. There is no point in that unless it has a
chance of being merged upstream, and I think depending on clang is a
non-starter for that. I'm just totally disinterested in having that
discussion.

Instead, I'm trying to make it a really small and clean alternative for
Doxygen in Sphinx based documentation.

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

  reply	other threads:[~2016-12-12 10:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 11:20 [PATCH] drm/i915/perf: More documentation hooked to i915.rst Robert Bragg
2016-12-05 12:16 ` Matthew Auld
2016-12-07 21:40   ` Robert Bragg
2016-12-08 15:53     ` Daniel Vetter
2016-12-09 12:41       ` Robert Bragg
2016-12-12  7:34         ` Daniel Vetter
2016-12-12 10:00           ` Jani Nikula [this message]
2016-12-05 13:55 ` ✗ Fi.CI.BAT: failure for drm/i915/perf: More documentation hooked to i915.rst (rev2) Patchwork
2016-12-05 14:25   ` Chris Wilson
2016-12-07 22:53 ` ✓ Fi.CI.BAT: success for drm/i915/perf: More documentation hooked to i915.rst (rev3) Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2016-11-29 17:00 [PATCH] drm/i915/perf: More documentation hooked to i915.rst Robert Bragg
2016-11-30 16:30 ` Matthew Auld
2016-11-30 19:41 ` Daniel Vetter
2016-12-01 12:12   ` Jani Nikula
2016-12-02 15:17     ` Robert Bragg
2016-12-02 15:05   ` Robert Bragg

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=878trlv551.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=robert@sixbynine.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.