doc: test-writing-guidelines: Add TERRNO and TTERRNO
* Add note about TERRNO and TTERRNO for ttype
* Update umask() paragraph a bit
Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
diff --git a/doc/test-writing-guidelines.txt b/doc/test-writing-guidelines.txt
index 7cdaf2f..0a2ac8f 100644
--- a/doc/test-writing-guidelines.txt
+++ b/doc/test-writing-guidelines.txt
@@ -400,6 +400,9 @@
| 'TINFO' | General message.
|==============================
+The 'ttype' can be combined bitwise with 'TERRNO' or 'TTERRNO' to print
+'errno', 'TEST_ERRNO' respectively.
+
[source,c]
-------------------------------------------------------------------------------
void tst_brkm(int ttype, void (*cleanup)(void), char *arg_fmt, ...);
@@ -414,6 +417,8 @@
| 'TFAIL' | test has failed
|============================================================
+The 'ttype' can be combined bitwise with 'TERRNO' or 'TTERRNO' to print
+'errno', 'TEST_ERRNO' respectively.
[source,c]
-------------------------------------------------------------------------------
@@ -946,8 +951,8 @@
with 'open()' or 'creat()' etc, the mode specified as the last parameter *is
not* the mode the file is created with. The mode depends on current 'umask()'
settings which may clear some of the bits. If your test depends on specific
-file permissions you need to 'chmod()' the file afterwards or use SAFE_TOUCH()
-that does the 'chmod()' for you.
+file permissions you need either to change umask to 0 or 'chmod()' the file
+afterwards or use SAFE_TOUCH() that does the 'chmod()' for you.
3.2 access()
~~~~~~~~~~~