intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm: Documentation style guide
Date: Wed, 09 Dec 2015 14:35:40 +0200	[thread overview]
Message-ID: <6562184.HVjBAtNVbF@avalon> (raw)
In-Reply-To: <87h9jrx3yy.fsf@intel.com>

On Wednesday 09 December 2015 13:21:09 Jani Nikula wrote:
> On Wed, 09 Dec 2015, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > Every time I type or review docs this seems a bit different. Try to
> > document the common style so we can try to unify at least new docs.
> > 
> > v2: Spelling fixes from Pierre, Laurent and Jani.
> 
> Nah, you ignored my comment about "these documentations use American
> English". :/

Isn't documentation uncountable when meaning information recorded in a 
document ?

-- 
Regards,

Laurent Pinchart

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

  reply	other threads:[~2015-12-09 12:35 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
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 [this message]
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=6562184.HVjBAtNVbF@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).