All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 1/5] [RFC] drm: Documentation style guide
Date: Tue, 8 Dec 2015 11:14:16 +0100	[thread overview]
Message-ID: <20151208101416.GG20822@phenom.ffwll.local> (raw)
In-Reply-To: <20151208095905.GA5523@Sovereign.cs.lth.se>

On Tue, Dec 08, 2015 at 10:59:05AM +0100, Pierre Moreau wrote:
> On 09:49 AM - Dec 08 2015, Daniel Vetter wrote:
> > +    <para>
> > +      Functions which have a non-<code>void</code> return value should have a
> > +      section called "Returns" explaining the expected return values in
> > +      different cases an their meanings. Currently there's no consensus whether
> > +      that section name should be all upper-case or not, and whether it should
> > +      end in a colon or not. Go with the file-local style. Other common section
> > +      names are "Notes" with information for dangerous or tricky corner cases,
> > +      and "FIXME" where the interface could be cleaned up.
> 
> Why not define (and use) a single style for naming all sections? Old
> documentation might not use it, but it should be doable to upgrade those old
> documents.

There is a massive pile of these docs, and there is a slight difference in
how vfunc table section headings and function reference section headings
are rendered. Given that I figured I'll start modestly.

But if you feel like making this consistent I'd definitely take a patch to
do so. Same really for any of the other style guideline issues. Well,
after we have some acks on this, and any large-scale style change should
first do the RFC patch for this section for discussion to avoid the risk
of wasting lots of time.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-12-08 10:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08  8:49 [PATCH 1/5] [RFC] drm: Documentation style guide Daniel Vetter
2015-12-08  8:49 ` [PATCH 2/5] drm/atomic-helper: Drop unneeded argument from check_pending_encoder Daniel Vetter
2015-12-14 15:58   ` Thierry Reding
2015-12-08  8:49 ` [PATCH 3/5] drm: Move more framebuffer doc from docbook to kerneldoc Daniel Vetter
2015-12-14 15:58   ` Thierry Reding
2015-12-14 17:25     ` Daniel Vetter
2015-12-08  8:49 ` [PATCH 4/5] drm/atomic-helper: Reject legacy flips on a disabled pipe Daniel Vetter
2015-12-08 12:01   ` [Intel-gfx] " Daniel Stone
2016-01-05  9:02     ` Daniel Vetter
2015-12-08 13:55   ` Ilia Mirkin
2015-12-08  8:49 ` [PATCH 5/5] drm/tda998x: Remove dummy save/restore funcs Daniel Vetter
2015-12-08  9:30   ` Emil Velikov
2015-12-08 10:11     ` Daniel Vetter
2015-12-08 10:15       ` Russell King - ARM Linux
2015-12-08 15:29         ` Rodrigo Vivi
2015-12-08  9:59 ` [PATCH 1/5] [RFC] drm: Documentation style guide Pierre Moreau
2015-12-08 10:14   ` Daniel Vetter [this message]
2015-12-08 13:49   ` Laurent Pinchart
2015-12-09 10:41     ` [PATCH] " Daniel Vetter
2015-12-09 10:44       ` Daniel Vetter
2015-12-09 11:21       ` Jani Nikula
2015-12-09 12:35         ` Laurent Pinchart
2015-12-09 14:17           ` Jani Nikula
2015-12-09 14:32             ` Laurent Pinchart
2015-12-09 13:35         ` Daniel Vetter
2015-12-09 15:19       ` Lukas Wunner
2015-12-09 16:08         ` Daniel Vetter
2015-12-14 15:39           ` Thierry Reding
2015-12-15 14:56             ` Dave Gordon
2015-12-15 16:09               ` 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=20151208101416.GG20822@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@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.