All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Anna Karas <anna.karas@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/perf: Fix use of kernel-doc format in structure members.
Date: Fri, 20 Sep 2019 13:17:48 +0300	[thread overview]
Message-ID: <ef4a2cd3-cba8-bfd1-cfe4-08245ef374ed@intel.com> (raw)
In-Reply-To: <20190920094727.18289-1-anna.karas@intel.com>

On 20/09/2019 12:47, Anna Karas wrote:
> Insert structure members names into their descriptions to follow
> kernel-doc format.
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Anna Karas <anna.karas@intel.com>

Acked-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>


> ---
>   drivers/gpu/drm/i915/i915_drv.h | 26 ++++++++++++++------------
>   1 file changed, 14 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index 0d1949a78c44..dc6c9f52d3a5 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -1225,7 +1225,7 @@ struct i915_perf_stream {
>   	struct i915_oa_config *oa_config;
>   
>   	/**
> -	 * The OA context specific information.
> +	 * @pinned_ctx: The OA context specific information.
>   	 */
>   	struct intel_context *pinned_ctx;
>   	u32 specific_ctx_id;
> @@ -1239,7 +1239,7 @@ struct i915_perf_stream {
>   	int period_exponent;
>   
>   	/**
> -	 * State of the OA buffer.
> +	 * @oa_buffer: State of the OA buffer.
>   	 */
>   	struct {
>   		struct i915_vma *vma;
> @@ -1250,7 +1250,7 @@ struct i915_perf_stream {
>   		int size_exponent;
>   
>   		/**
> -		 * Locks reads and writes to all head/tail state
> +		 * @ptr_lock: Locks reads and writes to all head/tail state
>   		 *
>   		 * Consider: the head and tail pointer state needs to be read
>   		 * consistently from a hrtimer callback (atomic context) and
> @@ -1272,8 +1272,8 @@ struct i915_perf_stream {
>   		spinlock_t ptr_lock;
>   
>   		/**
> -		 * One 'aging' tail pointer and one 'aged' tail pointer ready to
> -		 * used for reading.
> +		 * @tails: One 'aging' tail pointer and one 'aged' tail pointer
> +		 * ready to used for reading.
>   		 *
>   		 * Initial values of 0xffffffff are invalid and imply that an
>   		 * update is required (and should be ignored by an attempted
> @@ -1284,21 +1284,23 @@ struct i915_perf_stream {
>   		} tails[2];
>   
>   		/**
> -		 * Index for the aged tail ready to read() data up to.
> +		 * @aged_tail_idx: Index for the aged tail ready to read() data
> +		 * up to.
>   		 */
>   		unsigned int aged_tail_idx;
>   
>   		/**
> -		 * A monotonic timestamp for when the current aging tail pointer
> -		 * was read; used to determine when it is old enough to trust.
> +		 * @aging_timestamp: A monotonic timestamp for when the current
> +		 * aging tail pointer was read; used to determine when it is old
> +		 * enough to trust.
>   		 */
>   		u64 aging_timestamp;
>   
>   		/**
> -		 * Although we can always read back the head pointer register,
> -		 * we prefer to avoid trusting the HW state, just to avoid any
> -		 * risk that some hardware condition could * somehow bump the
> -		 * head pointer unpredictably and cause us to forward the wrong
> +		 * @head: Although we can always read back the head pointer
> +		 * register, we prefer to avoid trusting the HW state, just to
> +		 * avoid any risk that some hardware condition could somehow bump
> +		 * the head pointer unpredictably and cause us to forward the wrong
>   		 * OA buffer data to userspace.
>   		 */
>   		u32 head;


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-09-20 10:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 10:49 [PATCH] Docs: fix incorrect use of kernel-doc format in structure description Anna Karas
2019-09-19 11:00 ` Chris Wilson
2019-09-19 12:21   ` Jani Nikula
2019-09-19 12:17 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-09-19 19:18 ` ✓ Fi.CI.IGT: " Patchwork
2019-09-20  9:47 ` [PATCH] drm/i915/perf: Fix use of kernel-doc format in structure members Anna Karas
2019-09-20 10:17   ` Lionel Landwerlin [this message]
2019-09-20 14:20 ` ✓ Fi.CI.BAT: success for Docs: fix incorrect use of kernel-doc format in structure description. (rev2) Patchwork
2019-09-21 12:20 ` ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2019-09-26 12:21 [PATCH] drm/i915/perf: Fix use of kernel-doc format in structure members Anna Karas
2019-09-26 13:24 ` Lionel Landwerlin

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=ef4a2cd3-cba8-bfd1-cfe4-08245ef374ed@intel.com \
    --to=lionel.g.landwerlin@intel.com \
    --cc=anna.karas@intel.com \
    --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.