From: Alex Hung <alex.hung@amd.com>
To: <igt-dev@lists.freedesktop.org>
Cc: <harry.wentland@amd.com>, <alex.hung@amd.com>,
<aurabindo.pillai@amd.com>
Subject: [PATCH] tests/kms_writeback: fix coding style issues
Date: Wed, 8 Apr 2026 17:02:45 -0600 [thread overview]
Message-ID: <20260408230245.442843-1-alex.hung@amd.com> (raw)
Fix missing spaces after comma in two igt_skip_on_f() calls and
in the writeback-invalid-parameters subtest description strings.
Signed-off-by: Alex Hung <alex.hung@amd.com>
---
tests/kms_writeback.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/tests/kms_writeback.c b/tests/kms_writeback.c
index f15abba96..5031fcb83 100644
--- a/tests/kms_writeback.c
+++ b/tests/kms_writeback.c
@@ -58,8 +58,8 @@
* Description: Validate WRITEBACK_FB_ID with valid and invalid options
*
* SUBTEST: writeback-invalid-parameters
- * Description: Writeback has a couple of parameters linked together(output
- * framebuffer and fence); this test goes throughthe combination
+ * Description: Writeback has a couple of parameters linked together (output
+ * framebuffer and fence); this test goes through the combination
* of possible bad options
*
* SUBTEST: writeback-pixel-formats
@@ -620,8 +620,8 @@ int igt_main_args("b:c:f:dl", long_options, help_str, opt_handler, NULL)
drmModeFreePropertyBlob(formats_blob);
}
- igt_describe("Writeback has a couple of parameters linked together"
- "(output framebuffer and fence); this test goes through"
+ igt_describe("Writeback has a couple of parameters linked together "
+ "(output framebuffer and fence); this test goes through "
"the combination of possible bad options");
igt_subtest("writeback-invalid-parameters") {
igt_fb_t invalid_output_fb;
@@ -644,7 +644,7 @@ int igt_main_args("b:c:f:dl", long_options, help_str, opt_handler, NULL)
igt_fb_t output_fb;
igt_skip_on(data.dump_check || data.list_modes);
- igt_skip_on_f(!(data.supported_colors & XRGB8888),"DRM_FORMAT_XRGB8888 is unsupported\n");
+ igt_skip_on_f(!(data.supported_colors & XRGB8888), "DRM_FORMAT_XRGB8888 is unsupported\n");
fb_id = igt_create_fb(display.drm_fd, mode.hdisplay, mode.vdisplay,
DRM_FORMAT_XRGB8888,
DRM_FORMAT_MOD_LINEAR,
@@ -678,7 +678,7 @@ int igt_main_args("b:c:f:dl", long_options, help_str, opt_handler, NULL)
igt_fb_t output_fb;
igt_skip_on(data.dump_check || data.list_modes);
- igt_skip_on_f(!(data.supported_colors & XRGB8888),"DRM_FORMAT_XRGB8888 is unsupported\n");
+ igt_skip_on_f(!(data.supported_colors & XRGB8888), "DRM_FORMAT_XRGB8888 is unsupported\n");
fb_id = igt_create_fb(display.drm_fd, mode.hdisplay, mode.vdisplay,
DRM_FORMAT_XRGB8888,
igt_fb_mod_to_tiling(0),
--
2.43.0
next reply other threads:[~2026-04-08 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 23:02 Alex Hung [this message]
2026-04-09 8:06 ` [PATCH] tests/kms_writeback: fix coding style issues Kandpal, Suraj
2026-04-09 13:40 ` Kamil Konieczny
2026-04-09 22:35 ` ✗ Fi.CI.BAT: failure 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=20260408230245.442843-1-alex.hung@amd.com \
--to=alex.hung@amd.com \
--cc=aurabindo.pillai@amd.com \
--cc=harry.wentland@amd.com \
--cc=igt-dev@lists.freedesktop.org \
/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