From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Jose Souza <jose.souza@intel.com>
Subject: [PATCH] drm/i915: Add some boring kerneldoc
Date: Mon, 19 Feb 2024 13:25:17 +0000 [thread overview]
Message-ID: <20240219132517.1868604-1-tvrtko.ursulin@linux.intel.com> (raw)
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Tooling appears very strict so lets pacify it by adding some comments,
even if fields are completely self-explanatory.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Fixes: b11236486749 ("drm/i915: Add GuC submission interface version query")
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jose Souza <jose.souza@intel.com>
---
include/uapi/drm/i915_drm.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h
index bd87386a8243..2ee338860b7e 100644
--- a/include/uapi/drm/i915_drm.h
+++ b/include/uapi/drm/i915_drm.h
@@ -3572,9 +3572,13 @@ struct drm_i915_query_memory_regions {
* struct drm_i915_query_guc_submission_version - query GuC submission interface version
*/
struct drm_i915_query_guc_submission_version {
+ /** @branch: Firmware branch version. */
__u32 branch;
+ /** @major: Firmware major version. */
__u32 major;
+ /** @minor: Firmware minor version. */
__u32 minor;
+ /** @patch: Firmware patch version. */
__u32 patch;
};
--
2.40.1
next reply other threads:[~2024-02-19 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 13:25 Tvrtko Ursulin [this message]
2024-02-19 13:28 ` [PATCH] drm/i915: Add some boring kerneldoc Souza, Jose
2024-02-19 20:21 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2024-02-19 20:21 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-02-19 20:26 ` ✓ Fi.CI.BAT: success " Patchwork
2024-02-20 4:49 ` ✗ Fi.CI.IGT: 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=20240219132517.1868604-1-tvrtko.ursulin@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=tvrtko.ursulin@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.