Commit 10e3e5d4 authored by Daniel Vetter's avatar Daniel Vetter

lib: avoid < in gtkdoc comments

For reasons entirely not clear to me meson gtkdoc runs in strict
xml parsing mode, whereas automake gtkdoc doesn't. And gtkdoc itself
is tooooooooo dense to correctly escape this stuff.

Paper around this.

v2: {foo} instead of of tripy &lt;foo> (Joonas)

v3: More fixups (Joonas)

Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Reviewed-by: Petri Latvala's avatarPetri Latvala <petri.latvala@intel.com>
Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
parent 55da0751
......@@ -998,7 +998,7 @@ void igt_drop_root(void)
* @var: var lookup to to enable this wait
*
* Waits for a key press when run interactively and when the corresponding debug
* var is set in the --interactive-debug=<var> variable. Multiple keys
* var is set in the --interactive-debug=$var variable. Multiple keys
* can be specified as a comma-separated list or alternatively "all" if a wait
* should happen for all cases.
*
......@@ -1039,7 +1039,7 @@ void igt_debug_wait_for_keypress(const char *var)
* @expected: message to be printed as expected behaviour before wait for keys Y/n
*
* Waits for a key press when run interactively and when the corresponding debug
* var is set in the --interactive-debug=<var> variable. Multiple vars
* var is set in the --interactive-debug=$var variable. Multiple vars
* can be specified as a comma-separated list or alternatively "all" if a wait
* should happen for all cases.
*
......
......@@ -167,10 +167,10 @@
* test logic.
*
* - When adding a new feature test function which uses igt_skip() internally,
* use the <prefix>_require_<feature_name> naming scheme. When you
* use the {prefix}_require_{feature_name} naming scheme. When you
* instead add a feature test function which returns a boolean, because your
* main test logic must take different actions depending upon the feature's
* availability, then instead use the <prefix>_has_<feature_name>.
* availability, then instead use the {prefix}_has_{feature_name}.
*
* - As already mentioned eschew explicit error handling logic as much as
* possible. If your test absolutely has to handle the error of some function
......
......@@ -231,7 +231,7 @@ int igt_debugfs_dir(int device)
* @mode: mode bits as used by open()
*
* This opens a debugfs file as a Unix file descriptor. The filename should be
* relative to the drm device's root, i.e. without "drm/<minor>".
* relative to the drm device's root, i.e. without "drm/$minor".
*
* Returns:
* The Unix file descriptor for the debugfs file or -1 if that didn't work out.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment