All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Cc: intel-xe@lists.freedesktop.org, lucas.demarchi@intel.com,
	stuart.summers@intel.com
Subject: Re: [PATCH] drm/xe: Use correct function pointer type
Date: Tue, 19 Mar 2024 13:09:58 -0700	[thread overview]
Message-ID: <85msqu56g9.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20240319174919.1847-1-niranjana.vishwanathapura@intel.com>

On Tue, 19 Mar 2024 10:49:19 -0700, Niranjana Vishwanathapura wrote:
>
> Use xe_exec_queue_user_extension_fn type for
> exec_queue_user_extension_funcs.`
>
> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_exec_queue.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_exec_queue.c b/drivers/gpu/drm/xe/xe_exec_queue.c
> index 2016c1af9633..dd10188e8f4d 100644
> --- a/drivers/gpu/drm/xe/xe_exec_queue.c
> +++ b/drivers/gpu/drm/xe/xe_exec_queue.c
> @@ -388,7 +388,7 @@ typedef int (*xe_exec_queue_user_extension_fn)(struct xe_device *xe,
>					       struct xe_exec_queue *q,
>					       u64 extension);
>
> -static const xe_exec_queue_set_property_fn exec_queue_user_extension_funcs[] = {
> +static const xe_exec_queue_user_extension_fn exec_queue_user_extension_funcs[] = {
>	[DRM_XE_EXEC_QUEUE_EXTENSION_SET_PROPERTY] = exec_queue_user_ext_set_property,

The change is correct, though the types xe_exec_queue_set_property_fn and
xe_exec_queue_user_extension_fn are exactly the same (one has 'u64 value'
and the other 'u64 extension'). So it may even be possible to eliminte one
of them. That is why the compiler does not complain.

Anyway:

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



>  };
>
> --
> 2.43.0
>

  parent reply	other threads:[~2024-03-19 20:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 17:49 [PATCH] drm/xe: Use correct function pointer type Niranjana Vishwanathapura
2024-03-19 19:32 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-19 19:32 ` ✓ CI.checkpatch: " Patchwork
2024-03-19 19:34 ` ✓ CI.KUnit: " Patchwork
2024-03-19 19:44 ` ✓ CI.Build: " Patchwork
2024-03-19 19:47 ` ✓ CI.Hooks: " Patchwork
2024-03-19 19:48 ` ✓ CI.checksparse: " Patchwork
2024-03-19 20:09 ` Dixit, Ashutosh [this message]
2024-03-19 23:35   ` [PATCH] " Niranjana Vishwanathapura
2024-03-19 20:10 ` ✓ CI.BAT: success for " 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=85msqu56g9.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=niranjana.vishwanathapura@intel.com \
    --cc=stuart.summers@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.