From: "Santiago Millán via B4 Relay" <devnull+santimillang.gmail.com@kernel.org>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Daniel Stone <daniel@fooishbar.org>,
Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"kernel test robot" <lkp@intel.com>,
"Santiago Millán" <santimillang@gmail.com>
Subject: [PATCH] drm/tests: bridge: Document struct fmt_tuple members
Date: Wed, 14 Oct 2026 12:56:02 +0200 [thread overview]
Message-ID: <20261014-drm-bridge-test-kdoc-v1-1-883f7ec8bcfa@gmail.com> (raw)
From: Santiago Millán <santimillang@gmail.com>
The kernel-doc comment for struct fmt_tuple does not describe its
in_fmt and out_fmt members, so W=1 builds warn:
struct member 'in_fmt' not described in 'fmt_tuple'
struct member 'out_fmt' not described in 'fmt_tuple'
Add descriptions for both members.
Fixes: 082fbc179c01 ("drm/tests: bridge: Add KUnit tests for bridge chain format selection")
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202606120201.5E4O2N7N-lkp@intel.com/
Signed-off-by: Santiago Millán <santimillang@gmail.com>
---
drivers/gpu/drm/tests/drm_bridge_test.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/tests/drm_bridge_test.c b/drivers/gpu/drm/tests/drm_bridge_test.c
index 15583ade8494..b79d7b8b2d32 100644
--- a/drivers/gpu/drm/tests/drm_bridge_test.c
+++ b/drivers/gpu/drm/tests/drm_bridge_test.c
@@ -123,6 +123,8 @@ static const struct drm_bridge_funcs drm_test_bridge_bus_fmts_funcs = {
/**
* struct fmt_tuple - a tuple of input/output MEDIA_BUS_FMT_*
+ * @in_fmt: input bus format accepted by the bridge
+ * @out_fmt: output bus format the bridge can produce from @in_fmt
*/
struct fmt_tuple {
u32 in_fmt;
---
base-commit: dfc3c7b84d43e7de918686e5cd7dd49196a5f45e
change-id: 20261014-drm-bridge-test-kdoc-a46e4183b670
Best regards,
--
Santiago Millán <santimillang@gmail.com>
next reply other threads:[~2026-10-14 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 10:56 Santiago Millán via B4 Relay [this message]
2026-10-14 14:10 ` Nicolas Frattaroli
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=20261014-drm-bridge-test-kdoc-v1-1-883f7ec8bcfa@gmail.com \
--to=devnull+santimillang.gmail.com@kernel.org \
--cc=airlied@gmail.com \
--cc=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nicolas.frattaroli@collabora.com \
--cc=santimillang@gmail.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®