From: Eric Anholt <eric@anholt.net>
To: linux-doc@vger.kernel.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 4/6] drm/doc: Consistent kerneldoc include order
Date: Tue, 28 Feb 2017 15:39:51 -0800 [thread overview]
Message-ID: <87h93d3mwo.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <20170228171319.1786-5-daniel.vetter@ffwll.ch>
[-- Attachment #1.1: Type: text/plain, Size: 291 bytes --]
Daniel Vetter <daniel.vetter@ffwll.ch> writes:
> First overview text (if there is any), then headers (since generally
> you want to start out with the data structures), then all the other
> stuff with functions.
>
> Most of this is pre-shpinx, since with the old docbook only the
"sphinx"
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 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
next prev parent reply other threads:[~2017-02-28 23:39 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 17:13 [PATCH 0/6] more kernel-doc patches Daniel Vetter
2017-02-28 17:13 ` [PATCH 1/6] doc: Explain light-handed markup preference a bit better Daniel Vetter
2017-02-28 17:13 ` [PATCH 2/6] docs-rst: automatically convert Graphviz and SVG images Daniel Vetter
2017-03-01 15:56 ` Gabriel Krisman Bertazi
2017-03-02 7:12 ` Daniel Vetter
2017-03-02 8:23 ` Markus Heiser
2017-03-02 12:26 ` Laurent Pinchart
2017-03-02 13:54 ` Daniel Vetter
2017-03-02 14:14 ` Laurent Pinchart
2017-03-02 14:58 ` Markus Heiser
2017-03-02 15:11 ` Daniel Vetter
2017-03-02 15:17 ` Laurent Pinchart
2017-03-02 15:21 ` Markus Heiser
2017-03-02 15:45 ` Mauro Carvalho Chehab
2017-03-02 15:49 ` Mauro Carvalho Chehab
2017-03-02 16:13 ` Markus Heiser
2017-03-02 16:29 ` Mauro Carvalho Chehab
2017-03-02 18:16 ` Markus Heiser
2017-03-02 18:20 ` Jonathan Corbet
2017-03-02 18:47 ` Markus Heiser
2017-03-02 19:09 ` Mauro Carvalho Chehab
2017-03-02 20:16 ` Markus Heiser
2017-03-02 20:28 ` Mauro Carvalho Chehab
2017-03-04 14:56 ` docutils borkage (was: [PATCH 2/6] docs-rst: automatically convert Graphviz and SVG images) Jonathan Corbet
2017-03-05 2:23 ` Mauro Carvalho Chehab
2017-03-02 15:22 ` [PATCH 2/6] docs-rst: automatically convert Graphviz and SVG images Jonathan Corbet
2017-03-02 15:53 ` Daniel Vetter
2017-03-02 16:01 ` Mauro Carvalho Chehab
2017-03-02 19:49 ` Daniel Vetter
2017-03-06 10:12 ` Daniel Vetter
2017-03-06 13:13 ` Markus Heiser
2017-03-06 15:03 ` Daniel Vetter
2017-02-28 17:13 ` [PATCH 3/6] drm/doc: Add KMS overview graphs Daniel Vetter
2017-03-01 16:33 ` Gabriel Krisman Bertazi
2017-03-02 14:34 ` Laurent Pinchart
2017-03-02 15:06 ` Daniel Vetter
2017-02-28 17:13 ` [PATCH 4/6] drm/doc: Consistent kerneldoc include order Daniel Vetter
2017-02-28 23:39 ` Eric Anholt [this message]
2017-02-28 17:13 ` [PATCH 5/6] drm/doc: diagram for mode objects and properties Daniel Vetter
2017-02-28 23:40 ` Eric Anholt
2017-03-01 8:27 ` [PATCH] " Daniel Vetter
2017-03-01 16:45 ` Gabriel Krisman Bertazi
2017-03-02 14:42 ` Laurent Pinchart
2017-02-28 17:13 ` [PATCH 6/6] drm/doc: atomic overview, with graph Daniel Vetter
2017-02-28 23:48 ` Eric Anholt
2017-03-01 9:57 ` Daniel Vetter
2017-03-01 17:42 ` Gabriel Krisman Bertazi
2017-03-02 7:16 ` Daniel Vetter
2017-03-01 8:35 ` [PATCH] " Daniel Vetter
2017-03-01 17:42 ` Eric Anholt
2017-03-02 7:19 ` Daniel Vetter
2017-03-02 14:41 ` Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2017-03-02 15:16 [PATCH 1/6] doc: Explain light-handed markup preference a bit better Daniel Vetter
2017-03-02 15:16 ` [PATCH 4/6] drm/doc: Consistent kerneldoc include order Daniel Vetter
2016-12-19 7:44 [PATCH 0/6] diagrams for drm docs Daniel Vetter
2016-12-19 7:44 ` [PATCH 4/6] drm/doc: Consistent kerneldoc include order Daniel Vetter
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=87h93d3mwo.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.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.