Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, Zhanjun Dong <zhanjun.dong@intel.com>,
	Julia Filipchuk <julia.filipchuk@intel.com>,
	Ashutosh Dixit <ashutosh.dixit@intel.com>
Subject: [PATCH 1/5] drm/xe/guc: fix struct guc_lfd_file_header kernel-doc
Date: Wed,  7 Jan 2026 17:53:57 +0200	[thread overview]
Message-ID: <20260107155401.2379127-1-jani.nikula@intel.com> (raw)

Fix kernel-doc warnings on struct guc_lfd_file_header:

Warning: ../drivers/gpu/drm/xe/abi/guc_lfd_abi.h:168 expecting prototype
  for struct guc_logfile_header. Prototype was for struct
  guc_lfd_file_header instead

Fixes: 7eeb0e5408bd ("drm/xe/guc: Add LFD related abi definitions")
Cc: Zhanjun Dong <zhanjun.dong@intel.com>
Cc: Julia Filipchuk <julia.filipchuk@intel.com>
Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
 drivers/gpu/drm/xe/abi/guc_lfd_abi.h | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/drivers/gpu/drm/xe/abi/guc_lfd_abi.h b/drivers/gpu/drm/xe/abi/guc_lfd_abi.h
index b6ed20d5b508..5c48459f365f 100644
--- a/drivers/gpu/drm/xe/abi/guc_lfd_abi.h
+++ b/drivers/gpu/drm/xe/abi/guc_lfd_abi.h
@@ -148,7 +148,7 @@ struct guc_lfd_data_os_info {
 } __packed;
 
 /**
- * struct guc_logfile_header - Header of GuC Log Streaming-LFD-File Format.
+ * struct guc_lfd_file_header - Header of GuC Log Streaming-LFD-File Format.
  * This structure encapsulates the layout of the guc-log-file format
  */
 struct guc_lfd_file_header {
@@ -163,8 +163,7 @@ struct guc_lfd_file_header {
 #define GUC_LFD_FILE_HEADER_VERSION_MASK_MAJOR	GENMASK(31, 16)
 #define GUC_LFD_FILE_HEADER_VERSION_MASK_MINOR	GENMASK(15, 0)
 
-	/** @stream: A stream of one or more guc_lfd_data LFD blocks
-	 */
+	/** @stream: A stream of one or more guc_lfd_data LFD blocks */
 	u32 stream[];
 } __packed;
 
-- 
2.47.3


             reply	other threads:[~2026-01-07 15:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 15:53 Jani Nikula [this message]
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
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=20260107155401.2379127-1-jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=julia.filipchuk@intel.com \
    --cc=zhanjun.dong@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