All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@kernel.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 08/24] drm/i915/request: drop kernel-doc
Date: Wed, 3 May 2023 10:19:29 -0400	[thread overview]
Message-ID: <ZFJtcWKnIxnrcHdj@rdvivi-mobl4> (raw)
In-Reply-To: <62a7a0f6e5b33e59ef4339304d01e7ef7ee04430.1683041799.git.jani.nikula@intel.com>

On Tue, May 02, 2023 at 06:37:25PM +0300, Jani Nikula wrote:
> The documentation is closer to not being kernel-doc. Just drop the
> kernel-doc /** indicators.
> 
> drivers/gpu/drm/i915/i915_request.h:176: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
>  * Request queue structure.
> drivers/gpu/drm/i915/i915_request.h:477: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
>  * Returns true if seq1 is later than seq2.
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_request.h | 52 ++++++++++++++---------------
>  1 file changed, 26 insertions(+), 26 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_request.h b/drivers/gpu/drm/i915/i915_request.h
> index f5e1bb5e857a..0ac55b2e4223 100644
> --- a/drivers/gpu/drm/i915/i915_request.h
> +++ b/drivers/gpu/drm/i915/i915_request.h
> @@ -172,7 +172,7 @@ enum {
>  	I915_FENCE_FLAG_COMPOSITE,
>  };
>  
> -/**
> +/*
>   * Request queue structure.
>   *
>   * The request queue allows us to note sequence numbers that have been emitted
> @@ -198,7 +198,7 @@ struct i915_request {
>  
>  	struct drm_i915_private *i915;
>  
> -	/**
> +	/*
>  	 * Context and ring buffer related to this request
>  	 * Contexts are refcounted, so when this request is associated with a
>  	 * context, we must increment the context's refcount, to guarantee that
> @@ -251,9 +251,9 @@ struct i915_request {
>  	};
>  	struct llist_head execute_cb;
>  	struct i915_sw_fence semaphore;
> -	/**
> -	 * @submit_work: complete submit fence from an IRQ if needed for
> -	 * locking hierarchy reasons.
> +	/*
> +	 * complete submit fence from an IRQ if needed for locking hierarchy
> +	 * reasons.
>  	 */
>  	struct irq_work submit_work;
>  
> @@ -277,35 +277,35 @@ struct i915_request {
>  	 */
>  	const u32 *hwsp_seqno;
>  
> -	/** Position in the ring of the start of the request */
> +	/* Position in the ring of the start of the request */
>  	u32 head;
>  
> -	/** Position in the ring of the start of the user packets */
> +	/* Position in the ring of the start of the user packets */
>  	u32 infix;
>  
> -	/**
> +	/*
>  	 * Position in the ring of the start of the postfix.
>  	 * This is required to calculate the maximum available ring space
>  	 * without overwriting the postfix.
>  	 */
>  	u32 postfix;
>  
> -	/** Position in the ring of the end of the whole request */
> +	/* Position in the ring of the end of the whole request */
>  	u32 tail;
>  
> -	/** Position in the ring of the end of any workarounds after the tail */
> +	/* Position in the ring of the end of any workarounds after the tail */
>  	u32 wa_tail;
>  
> -	/** Preallocate space in the ring for the emitting the request */
> +	/* Preallocate space in the ring for the emitting the request */
>  	u32 reserved_space;
>  
> -	/** Batch buffer pointer for selftest internal use. */
> +	/* Batch buffer pointer for selftest internal use. */
>  	I915_SELFTEST_DECLARE(struct i915_vma *batch);
>  
>  	struct i915_vma_resource *batch_res;
>  
>  #if IS_ENABLED(CONFIG_DRM_I915_CAPTURE_ERROR)
> -	/**
> +	/*
>  	 * Additional buffers requested by userspace to be captured upon
>  	 * a GPU hang. The vma/obj on this list are protected by their
>  	 * active reference - all objects on this list must also be
> @@ -314,29 +314,29 @@ struct i915_request {
>  	struct i915_capture_list *capture_list;
>  #endif
>  
> -	/** Time at which this request was emitted, in jiffies. */
> +	/* Time at which this request was emitted, in jiffies. */
>  	unsigned long emitted_jiffies;
>  
> -	/** timeline->request entry for this request */
> +	/* timeline->request entry for this request */
>  	struct list_head link;
>  
> -	/** Watchdog support fields. */
> +	/* Watchdog support fields. */
>  	struct i915_request_watchdog {
>  		struct llist_node link;
>  		struct hrtimer timer;
>  	} watchdog;
>  
> -	/**
> -	 * @guc_fence_link: Requests may need to be stalled when using GuC
> -	 * submission waiting for certain GuC operations to complete. If that is
> -	 * the case, stalled requests are added to a per context list of stalled
> -	 * requests. The below list_head is the link in that list. Protected by
> +	/*
> +	 * Requests may need to be stalled when using GuC submission waiting for
> +	 * certain GuC operations to complete. If that is the case, stalled
> +	 * requests are added to a per context list of stalled requests. The
> +	 * below list_head is the link in that list. Protected by
>  	 * ce->guc_state.lock.
>  	 */
>  	struct list_head guc_fence_link;
>  
> -	/**
> -	 * @guc_prio: Priority level while the request is in flight. Differs
> +	/*
> +	 * Priority level while the request is in flight. Differs
>  	 * from i915 scheduler priority. See comment above
>  	 * I915_SCHEDULER_CAP_STATIC_PRIORITY_MAP for details. Protected by
>  	 * ce->guc_active.lock. Two special values (GUC_PRIO_INIT and
> @@ -348,8 +348,8 @@ struct i915_request {
>  #define	GUC_PRIO_FINI	0xfe
>  	u8 guc_prio;
>  
> -	/**
> -	 * @hucq: wait queue entry used to wait on the HuC load to complete
> +	/*
> +	 * wait queue entry used to wait on the HuC load to complete
>  	 */
>  	wait_queue_entry_t hucq;
>  
> @@ -473,7 +473,7 @@ i915_request_has_initial_breadcrumb(const struct i915_request *rq)
>  	return test_bit(I915_FENCE_FLAG_INITIAL_BREADCRUMB, &rq->fence.flags);
>  }
>  
> -/**
> +/*
>   * Returns true if seq1 is later than seq2.
>   */

hmmm... or all of these or properly move everything else to look like kernel doc,
but looking to this struct, let's just do this for now...


Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>


>  static inline bool i915_seqno_passed(u32 seq1, u32 seq2)
> -- 
> 2.39.2
> 

  reply	other threads:[~2023-05-03 14:19 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 15:37 [Intel-gfx] [PATCH 00/24] drm/i915: fix kernel-doc warnings, enable kernel-doc -Werror Jani Nikula
2023-05-02 15:37 ` [Intel-gfx] [PATCH 01/24] drm/i915/gvt: fix intel_vgpu_alloc_resource() kernel-doc parameter Jani Nikula
2023-05-03 14:07   ` Rodrigo Vivi
2023-05-04  9:15     ` Jani Nikula
2023-05-02 15:37 ` [Intel-gfx] [PATCH 02/24] drm/i915/vma: fix kernel-doc function name for i915_vma_size() Jani Nikula
2023-05-03 14:08   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 03/24] drm/i915/utils: drop kernel-doc from __wait_for() Jani Nikula
2023-05-03 14:09   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 04/24] drm/i915/vma: document struct i915_vma_resource wakeref member Jani Nikula
2023-05-03 14:16   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 05/24] drm/i915/vma: fix struct i915_vma_bindinfo kernel-doc Jani Nikula
2023-05-03 14:13   ` Rodrigo Vivi
2023-05-04  9:43     ` Jani Nikula
2023-05-04 14:54       ` Rodrigo Vivi
2023-05-04 21:51         ` Jani Nikula
2023-05-05 10:30         ` Jani Nikula
2023-05-02 15:37 ` [Intel-gfx] [PATCH 06/24] drm/i915/perf: fix i915_perf_ioctl_version() kernel-doc Jani Nikula
2023-05-03 14:14   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 07/24] drm/i915/error: fix i915_capture_error_state() kernel-doc Jani Nikula
2023-05-03 14:15   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 08/24] drm/i915/request: drop kernel-doc Jani Nikula
2023-05-03 14:19   ` Rodrigo Vivi [this message]
2023-05-02 15:37 ` [Intel-gfx] [PATCH 09/24] drm/i915/gem: fix i915_gem_object_lookup_rcu() kernel-doc parameter name Jani Nikula
2023-05-03 14:20   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 10/24] drm/i915/gem: fix function pointer member kernel-doc Jani Nikula
2023-05-03 14:24   ` Rodrigo Vivi
2023-05-04  9:20     ` Jani Nikula
2023-05-04 14:55       ` Rodrigo Vivi
2023-05-04 21:53         ` Jani Nikula
2023-05-05 10:30         ` Jani Nikula
2023-05-02 15:37 ` [Intel-gfx] [PATCH 11/24] drm/i915/ttm: fix i915_ttm_to_gem() kernel-doc Jani Nikula
2023-05-03 14:27   ` Rodrigo Vivi
2023-05-04  9:24     ` Jani Nikula
2023-05-02 15:37 ` [Intel-gfx] [PATCH 12/24] drm/i915/engine: fix kernel-doc function name for intel_engine_cleanup_common() Jani Nikula
2023-05-03 14:28   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 13/24] drm/i915/context: fix kernel-doc parameter descriptions Jani Nikula
2023-05-03 14:29   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 14/24] drm/i915/gtt: fix i915_vm_resv_put() kernel-doc parameter name Jani Nikula
2023-05-03 14:29   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 15/24] drm/i915/engine: hide preempt_hang selftest member from kernel-doc Jani Nikula
2023-05-03 14:34   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 16/24] drm/i915/guc: add dbgfs_node member kernel-doc Jani Nikula
2023-05-03 14:34   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 17/24] drm/i915/guc: drop lots of kernel-doc markers Jani Nikula
2023-05-03 14:37   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 18/24] drm/i915/guc: add intel_guc_state_capture member docs for ads_null_cache and max_mmio_per_node Jani Nikula
2023-05-03 14:38   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 19/24] drm/i915/active: fix kernel-doc for function parameters Jani Nikula
2023-05-03 14:38   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 20/24] drm/i915/pmu: drop kernel-doc Jani Nikula
2023-05-03 14:39   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 21/24] drm/i915/pxp: fix kernel-doc for member dev_link Jani Nikula
2023-05-03 14:40   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 22/24] drm/i915/scatterlist: fix kernel-doc Jani Nikula
2023-05-04 14:56   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 23/24] drm/i915/scatterlist: fix kernel-doc parameter documentation Jani Nikula
2023-05-03 14:40   ` Rodrigo Vivi
2023-05-02 15:37 ` [Intel-gfx] [PATCH 24/24] drm/i915: use kernel-doc -Werror when CONFIG_DRM_I915_WERROR=y Jani Nikula
2023-05-03 14:41   ` Rodrigo Vivi
2023-05-02 16:39 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: fix kernel-doc warnings, enable kernel-doc -Werror Patchwork
2023-05-02 16:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-02 18:37 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-05-04 18:19 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: fix kernel-doc warnings, enable kernel-doc -Werror (rev2) Patchwork

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=ZFJtcWKnIxnrcHdj@rdvivi-mobl4 \
    --to=rodrigo.vivi@kernel.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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 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.