All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
	Daniel Vetter <daniel.vetter@intel.com>,
	DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/5] drm/docs: Discourage adding more to kms-properties.csv
Date: Wed, 21 Feb 2018 02:23:30 +0200	[thread overview]
Message-ID: <33031482.45yx75NZS9@avalon> (raw)
In-Reply-To: <20180219225356.24996-1-daniel.vetter@ffwll.ch>

Hi Daniel,

Thank you for the patch.

On Tuesday, 20 February 2018 00:53:52 EET Daniel Vetter wrote:
> Motivated by patch review.
> 
> The table is really hard to read in source form, hard to edit, and
> we've moved away to more focused sections about specific features and
> how they're exposed in properties.
> 
> Those sections can then more easily enumerate options, link to helper
> functions and other parts of the docs. All things that get ugly real
> fast in the docs.
> 
> Cc: Maxime Ripard <maxime.ripard@bootlin.com>
> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>

Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

> ---
>  Documentation/gpu/drm-kms.rst | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/gpu/drm-kms.rst b/Documentation/gpu/drm-kms.rst
> index 2dcf5b42015d..56a3780e39b8 100644
> --- a/Documentation/gpu/drm-kms.rst
> +++ b/Documentation/gpu/drm-kms.rst
> @@ -547,8 +547,9 @@ Explicit Fencing Properties
>  Existing KMS Properties
>  -----------------------
> 
> -The following table gives description of drm properties exposed by
> -various modules/drivers.
> +The following table gives description of drm properties exposed by various
> +modules/drivers. Because this table is very unwieldy, do not add any new
> +properties here. Instead document them in a section above.
> 
>  .. csv-table::
>     :header-rows: 1

-- 
Regards,

Laurent Pinchart

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

      parent reply	other threads:[~2018-02-21  0:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 22:53 [PATCH 1/5] drm/docs: Discourage adding more to kms-properties.csv Daniel Vetter
2018-02-19 22:53 ` [PATCH 2/5] drm/docs: Align layout of optional plane blending properties Daniel Vetter
2018-02-20  9:42   ` Thierry Reding
2018-02-19 22:53 ` [PATCH 3/5] drm/docs: Document "scaling mode" property better Daniel Vetter
2018-02-20  9:45   ` Thierry Reding
2018-02-19 22:53 ` [PATCH 4/5] drm/doc: Polish for drm_mode_parse_command_line_for_connector Daniel Vetter
2018-02-20  9:46   ` Thierry Reding
2018-02-19 22:53 ` [PATCH 5/5] drm/doc: Use new substruct support Daniel Vetter
2018-02-20  9:49   ` Thierry Reding
2018-02-20 11:10     ` Daniel Vetter
2018-02-20 11:22       ` Thierry Reding
2018-02-20 13:25         ` Daniel Vetter
2018-02-20 11:23     ` Jani Nikula
2018-02-20  9:41 ` [PATCH 1/5] drm/docs: Discourage adding more to kms-properties.csv Thierry Reding
2018-02-21  0:23 ` Laurent Pinchart [this message]

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=33031482.45yx75NZS9@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maxime.ripard@bootlin.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 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.