public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/perf: Fix kernel-doc warning
Date: Mon, 07 Nov 2022 12:40:12 -0800	[thread overview]
Message-ID: <87r0yelcr7.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20221107202410.1976895-1-umesh.nerlige.ramappa@intel.com>

On Mon, 07 Nov 2022 12:24:10 -0800, Umesh Nerlige Ramappa wrote:
>
> Fix kernel-doc issue from a previous commit.

Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>

> Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
> Fixes: 2db609c01495 ("drm/i915/perf: Replace gt->perf.lock with stream->lock for file ops")
> ---
>  drivers/gpu/drm/i915/i915_perf_types.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_perf_types.h b/drivers/gpu/drm/i915/i915_perf_types.h
> index e0c96b44eda8..ca150b7af3f2 100644
> --- a/drivers/gpu/drm/i915/i915_perf_types.h
> +++ b/drivers/gpu/drm/i915/i915_perf_types.h
> @@ -146,8 +146,8 @@ struct i915_perf_stream {
>	 */
>	struct intel_engine_cs *engine;
>
> -	/*
> -	 * Lock associated with operations on stream
> +	/**
> +	 * @lock: Lock associated with operations on stream
>	 */
>	struct mutex lock;
>
> --
> 2.36.1
>

  reply	other threads:[~2022-11-07 20:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 20:24 [Intel-gfx] [PATCH] drm/i915/perf: Fix kernel-doc warning Umesh Nerlige Ramappa
2022-11-07 20:40 ` Dixit, Ashutosh [this message]
2022-11-08  0:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-11-08  1:01 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=87r0yelcr7.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=umesh.nerlige.ramappa@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