Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: Jani Nikula <jani.nikula@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 3/5] drm/xe/xe_late_bind_fw: fix enum xe_late_bind_fw_id kernel-doc
Date: Wed, 7 Jan 2026 23:09:45 +0530	[thread overview]
Message-ID: <d326b43f-0d6d-47ec-86b8-5147deff64e4@intel.com> (raw)
In-Reply-To: <20260107155401.2379127-3-jani.nikula@intel.com>


On 07-01-2026 21:23, Jani Nikula wrote:
> Fix kernel-doc warnings on enum xe_late_bind_fw_id:
>
> Warning: ../drivers/gpu/drm/xe/xe_late_bind_fw_types.h:19 cannot
>    understand function prototype: 'enum xe_late_bind_fw_id'
>
> Fixes: 45832bf9c10f ("drm/xe/xe_late_bind_fw: Initialize late binding firmware")
> Cc: Badal Nilawar <badal.nilawar@intel.com>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>   drivers/gpu/drm/xe/xe_late_bind_fw_types.h | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_late_bind_fw_types.h b/drivers/gpu/drm/xe/xe_late_bind_fw_types.h
> index 0f5da89ce98b..2a8a985c37e7 100644
> --- a/drivers/gpu/drm/xe/xe_late_bind_fw_types.h
> +++ b/drivers/gpu/drm/xe/xe_late_bind_fw_types.h
> @@ -15,10 +15,12 @@
>   #define XE_LB_MAX_PAYLOAD_SIZE SZ_4K
>   
>   /**
> - * xe_late_bind_fw_id - enum to determine late binding fw index
> + * enum xe_late_bind_fw_id - enum to determine late binding fw index
>    */
>   enum xe_late_bind_fw_id {
> +	/** @XE_LB_FW_FAN_CONTROL: Fan control */
>   	XE_LB_FW_FAN_CONTROL = 0,
> +	/** @XE_LB_FW_MAX_ID: Number of IDs */
>   	XE_LB_FW_MAX_ID
>   };

Reviewed-by: Badal Nilawar <badal.nilawar@intel.com>

>   

  reply	other threads:[~2026-01-07 17:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 15:53 [PATCH 1/5] drm/xe/guc: fix struct guc_lfd_file_header kernel-doc Jani Nikula
2026-01-07 15:53 ` [PATCH 2/5] drm/xe/vf: fix struct xe_gt_sriov_vf_migration kernel-doc Jani Nikula
2026-01-07 17:45   ` Matt Roper
2026-01-07 15:53 ` [PATCH 3/5] drm/xe/xe_late_bind_fw: fix enum xe_late_bind_fw_id kernel-doc Jani Nikula
2026-01-07 17:39   ` Nilawar, Badal [this message]
2026-01-07 15:54 ` [PATCH 4/5] drm/xe/vm: fix xe_vm_validation_exec() kernel-doc Jani Nikula
2026-01-07 17:49   ` Matt Roper
2026-01-07 15:54 ` [PATCH 5/5] drm/xe: improve header check Jani Nikula
2026-01-07 18:00   ` Matt Roper
2026-01-09  9:12     ` Jani Nikula
2026-01-09 15:41       ` Jani Nikula
2026-01-07 16:01 ` ✓ CI.KUnit: success for series starting with [1/5] drm/xe/guc: fix struct guc_lfd_file_header kernel-doc Patchwork
2026-01-07 16:43 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-07 17:44 ` [PATCH 1/5] " Matt Roper
2026-01-07 17:59 ` Dong, Zhanjun
2026-01-07 18:29 ` ✗ Xe.CI.Full: failure for series starting with [1/5] " 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=d326b43f-0d6d-47ec-86b8-5147deff64e4@intel.com \
    --to=badal.nilawar@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=rodrigo.vivi@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