All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [Intel-gfx] [PATCH 19/24] drm/i915/active: fix kernel-doc for function parameters
Date: Tue,  2 May 2023 18:37:36 +0300	[thread overview]
Message-ID: <7f201c6cb715e4b3cece78ffa893a75610ecd27d.1683041799.git.jani.nikula@intel.com> (raw)
In-Reply-To: <cover.1683041799.git.jani.nikula@intel.com>

drivers/gpu/drm/i915/i915_active.h:66: warning: Function parameter or member 'active' not described in '__i915_active_fence_init'
drivers/gpu/drm/i915/i915_active.h:66: warning: Function parameter or member 'fence' not described in '__i915_active_fence_init'
drivers/gpu/drm/i915/i915_active.h:66: warning: Function parameter or member 'fn' not described in '__i915_active_fence_init'
drivers/gpu/drm/i915/i915_active.h:89: warning: Function parameter or member 'active' not described in 'i915_active_fence_set'
drivers/gpu/drm/i915/i915_active.h:89: warning: Function parameter or member 'rq' not described in 'i915_active_fence_set'
drivers/gpu/drm/i915/i915_active.h:102: warning: Function parameter or member 'active' not described in 'i915_active_fence_get'
drivers/gpu/drm/i915/i915_active.h:122: warning: Function parameter or member 'active' not described in 'i915_active_fence_isset'

Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
 drivers/gpu/drm/i915/i915_active.h | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/drivers/gpu/drm/i915/i915_active.h b/drivers/gpu/drm/i915/i915_active.h
index 7eb44132183a..77c676ecc263 100644
--- a/drivers/gpu/drm/i915/i915_active.h
+++ b/drivers/gpu/drm/i915/i915_active.h
@@ -49,9 +49,9 @@ void i915_active_noop(struct dma_fence *fence, struct dma_fence_cb *cb);
 
 /**
  * __i915_active_fence_init - prepares the activity tracker for use
- * @active - the active tracker
- * @fence - initial fence to track, can be NULL
- * @func - a callback when then the tracker is retired (becomes idle),
+ * @active: the active tracker
+ * @fence: initial fence to track, can be NULL
+ * @fn: a callback when then the tracker is retired (becomes idle),
  *         can be NULL
  *
  * i915_active_fence_init() prepares the embedded @active struct for use as
@@ -77,8 +77,8 @@ __i915_active_fence_set(struct i915_active_fence *active,
 
 /**
  * i915_active_fence_set - updates the tracker to watch the current fence
- * @active - the active tracker
- * @rq - the request to watch
+ * @active: the active tracker
+ * @rq: the request to watch
  *
  * i915_active_fence_set() watches the given @rq for completion. While
  * that @rq is busy, the @active reports busy. When that @rq is signaled
@@ -89,7 +89,7 @@ i915_active_fence_set(struct i915_active_fence *active,
 		      struct i915_request *rq);
 /**
  * i915_active_fence_get - return a reference to the active fence
- * @active - the active tracker
+ * @active: the active tracker
  *
  * i915_active_fence_get() returns a reference to the active fence,
  * or NULL if the active tracker is idle. The reference is obtained under RCU,
@@ -111,7 +111,7 @@ i915_active_fence_get(struct i915_active_fence *active)
 
 /**
  * i915_active_fence_isset - report whether the active tracker is assigned
- * @active - the active tracker
+ * @active: the active tracker
  *
  * i915_active_fence_isset() returns true if the active tracker is currently
  * assigned to a fence. Due to the lazy retiring, that fence may be idle
-- 
2.39.2


  parent reply	other threads:[~2023-05-02 15:39 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
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 ` Jani Nikula [this message]
2023-05-03 14:38   ` [Intel-gfx] [PATCH 19/24] drm/i915/active: fix kernel-doc for function parameters 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=7f201c6cb715e4b3cece78ffa893a75610ecd27d.1683041799.git.jani.nikula@intel.com \
    --to=jani.nikula@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.