public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: sagar.a.kamble@intel.com, intel-gfx@lists.freedesktop.org
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	linux-doc@vger.kernel.org, Daniel Vetter <daniel.vetter@ffwll.ch>,
	Rob Landley <rob@landley.net>,
	David Herrmann <dh.herrmann@gmail.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	Dave Airlie <airlied@redhat.com>
Subject: Re: [PATCH v3 1/1] Documentation: drm: describing drm properties exposed by various drivers
Date: Fri, 07 Mar 2014 10:44:54 -0800	[thread overview]
Message-ID: <531A13A6.1030108@infradead.org> (raw)
In-Reply-To: <1394116069-18603-1-git-send-email-sagar.a.kamble@intel.com>

On 03/06/2014 06:27 AM, sagar.a.kamble@intel.com wrote:
> From: Sagar Kamble <sagar.a.kamble@intel.com>
> 
> Started documenting drm properties for drm drivers. This patch provides
> information about properties in drm, i915, psb and cdv/gma-500. Information
> about other properties can be added on top of these.
> 
> v2: Added description of drm properties in armada, exynos, i2c/ch7006, noveau,
> omap, qxl, radeon, rcar-du
> 
> v3: Removed "Property Object" column since it is implementation related. Property
> type column refined.[Ville's review comments]
> 
> Cc: Rob Landley <rob@landley.net>
> Cc: Dave Airlie <airlied@redhat.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> Cc: David Herrmann <dh.herrmann@gmail.com>
> Cc: Alex Deucher <alexander.deucher@amd.com>
> Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
> Cc: Sagar Kamble <sagar.a.kamble@intel.com>
> Cc: "Purushothaman, Vijay A" <vijay.a.purushothaman@intel.com>
> Cc: linux-doc@vger.kernel.org
> 
> Signed-off-by: Sagar Kamble <sagar.a.kamble@intel.com>
> ---
>  Documentation/DocBook/drm.tmpl | 1025 ++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 1025 insertions(+)

Warning: trailing whitespace in lines 2335,2345,2356,2367,2377,2390,2402,2411,2419,2427,2435,2443,2451,2459,2467,2475,2483,2491,2503,2513,2525,2536,2544,2554,2562,2570,2578,2586,2594,2602,2610,2618,2626,2634,2642,2650,2658,2666,2674,2682,2691,2702,2712,2720,2730,2738,2748,2756,2764,2772,2780,2788,2796,2804,2812,2820,2828,2836,2844,2852,2860,2868,2876,2885,2897,2907,2916,2924,2932,2940,2948,2963,2971,2979,2987,2998,3007,3017,3026,3036,3046,3054,3062,3070,3078,3086,3095,3103,3115,3129,3140,3148,3156,3164,3172,3181,3196,3204,3214,3224,3233,3249,3259,3270,3278,3286,3297,3307,3316,3326,3334,3342 of Documentation/DocBook/drm.tmpl

Please drop the trailing whitespace.


+     Following table gives description of drm properties exposed by various
+     modules/drivers.

      The following table ....



thanks.
-- 
~Randy
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2014-03-07 18:44 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 10:56 [PATCH 1/1] Documentation: drm: describing drm properties exposed by various drivers sagar.a.kamble
2014-03-06  7:15 ` [PATCH v2 " sagar.a.kamble
2014-03-06 12:09   ` Ville Syrjälä
2014-03-06 14:01     ` Sagar Arun Kamble
2014-03-06 14:27       ` [PATCH v3 " sagar.a.kamble
2014-03-07 18:44         ` Randy Dunlap [this message]
2014-03-08  6:33         ` [PATCH v4 " sagar.a.kamble
2014-03-08  7:28           ` [PATCH v5 " sagar.a.kamble
2014-03-10 14:33             ` Laurent Pinchart
2014-03-11 10:37               ` [PATCH v6 " sagar.a.kamble
2014-03-11 11:22                 ` Laurent Pinchart
2014-03-11 14:25                   ` [PATCH v7 " sagar.a.kamble
2014-03-11 14:31                     ` Laurent Pinchart
2014-03-11 13:13                 ` [PATCH v6 " Deucher, Alexander
2014-03-11 14:07                   ` Sagar Arun Kamble
2014-03-06 14:41       ` [PATCH v3 " sagar.a.kamble
2014-03-10  5:21 ` [PATCH " Daniel Vetter
2014-03-10 14:36   ` Laurent Pinchart
2014-03-12 11:16     ` Sagar Arun Kamble
2014-03-12 11:25       ` Laurent Pinchart
2014-05-10 10:39         ` Ville Syrjälä
2014-05-10 10:56           ` Rob Clark
2014-05-12  6:07             ` Sagar Arun Kamble
2014-05-12  8:03               ` Daniel Vetter
2014-05-13  7:17                 ` Thierry Reding
2014-05-13  7:34                   ` Daniel Vetter
2014-05-13  9:05                     ` Thierry Reding
2014-05-13 11:02                     ` Laurent Pinchart
2014-05-13 11:51                       ` Daniel Vetter
2014-05-12  8:24           ` Dave Airlie
2014-05-12  8:58             ` Daniel Vetter
2014-05-12 15:23               ` Randy Dunlap
2014-05-12 15:54                 ` Daniel Vetter
2014-05-12 18:04                   ` Randy Dunlap
2014-07-31 22:16                     ` Randy Dunlap
2014-08-01 12:58                       ` Laurent Pinchart
2014-08-01 22:21                         ` Randy Dunlap
2014-08-04  7:30                         ` Daniel Vetter
2014-08-04 13:58                           ` Laurent Pinchart

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=531A13A6.1030108@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=airlied@redhat.com \
    --cc=alexander.deucher@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dh.herrmann@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=sagar.a.kamble@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