From: Petri Latvala <petri.latvala@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>
Subject: [igt-dev] [PATCH i-g-t] lib/kms: Fix documentation for for_each_pipe_static
Date: Mon, 17 Dec 2018 14:43:23 +0200 [thread overview]
Message-ID: <20181217124323.5274-1-petri.latvala@intel.com> (raw)
The documentation block was copypasted from for_each_pipe without
changing the name.
A drive-by typo fix to for_each_pipe's docs is included.
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
---
lib/igt_kms.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/igt_kms.h b/lib/igt_kms.h
index 09395360..4a7c3c97 100644
--- a/lib/igt_kms.h
+++ b/lib/igt_kms.h
@@ -461,7 +461,7 @@ static inline bool igt_output_is_connected(igt_output_t *output)
igt_output_is_connected((output))))
/**
- * for_each_pipe:
+ * for_each_pipe_static:
* @pipe: The pipe to iterate.
*
* This for loop iterates over all pipes supported by IGT libraries.
@@ -481,7 +481,7 @@ static inline bool igt_output_is_connected(igt_output_t *output)
*
* Note that this cannot be used to enumerate per-pipe subtest names since it
* depends upon runtime probing of the actual kms driver that is being tested.
- * Used #for_each_pipe_static instead.
+ * Use #for_each_pipe_static instead.
*/
#define for_each_pipe(display, pipe) \
for (pipe = 0; assert(igt_can_fail()), pipe < igt_display_get_n_pipes(display); pipe++)
--
2.19.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2018-12-17 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 12:43 Petri Latvala [this message]
2018-12-17 13:03 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/kms: Fix documentation for for_each_pipe_static Patchwork
2018-12-17 14:18 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-12-27 12:54 ` Arkadiusz Hiler
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=20181217124323.5274-1-petri.latvala@intel.com \
--to=petri.latvala@intel.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