Many pages: Use man3type/ and man2type/ for type pages

Quoting Ingo:

[
The mandoc(1) program is also able to handle paths like
"man3/id_t.3type".  It will consider that page to be *both* in section
"3" (as specified by the directory name) and in section "3type" (as
specified by the file name and by the .TH macro).  I would consider
it better style to keep section names consistent, i.e. to use either
"man3/id_t.3" .TH id_t 3 or "man3type/id_t.3type" .TH id_t 3type,
but it's not a big deal: since many systems (in particular various
Linux distros) suffer from such inconsistencies, handling such
inconsistencies gracefully is an important feature that certainly
won't get removed.
]

Let's be nice, and do things right here, in the hope that others
may follow the example.

===

Most of this patch has been scripted:

$ mkdir man2type man3type
$ find man2 | grep type$ | while read f; do mv -t man2type $f; done
$ find man3 | grep type$ | while read f; do mv -t man3type $f; done
$ grep -rl man3/.*type man* | xargs sed -i 's,man3/,man3type/,'

Apart from that, I adapted the Makefiles, and moved va_list into
the man3type subsection (it was accidentally placed in the main 3
section).

Link: <https://lore.kernel.org/linux-man/YrB66rgFZqryrmpt@asta-kit.de/T/#u>
Reported-by: Ingo Schwarze <schwarze@usta.de>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>

1 files changed, 51 insertions, 0 deletions

diff --git a/man2type/open_how.2type b/man2type/open_how.2type
new file mode 100644
index 000000000..e058c08dc
--- /dev/null
+++ b/man2type/open_how.2type
@@ -0,0 +1,51 @@
+.\" Copyright (c) 2022 by Alejandro Colomar <colomar.6.4.3@gmail.com>
+.\"
+.\" SPDX-License-Identifier: Linux-man-pages-copyleft
+.\"
+.\"
+.TH OPEN_HOW 2type 2022-06-16 Linux "Linux Programmer's Manual"
+.SH NAME
+open_how \- how to open a pathname
+.SH LIBRARY
+Linux kernel headers
+.SH SYNOPSIS
+.nf
+.B #include <linux/openat2.h>
+.PP
+.B struct open_how {
+.BR "    u64  flags;" "    /* " O_ "* flags */"
+.BR "    u64  mode;" "     /* Mode for " O_ { CREAT , TMPFILE "} */"
+.BR "    u64  resolve;" "  /* " RESOLVE_ "* flags */"
+    /* ... */
+.B };
+.fi
+.SH DESCRIPTION
+Specifies how a pathname should be open.
+.PP
+The fields are as follows:
+.TP
+.I flags
+This field specifies the file creation and file status flags
+to use when opening the file.
+.TP
+.I mode
+This field specifies the mode for the new file.
+.TP
+.I resolve
+This is a bit mask of flags that modify the way in which
+.I all
+components of a pathname will be resolved
+(see
+.BR path_resolution (7)
+for background information).
+.SH VERSIONS
+Extra fields may be appended to the structure,
+with a zero value in a new field resulting in
+the kernel behaving as though that extension field was not present.
+Therefore, a user
+.I must
+zero-fill this structure on initialization.
+.SH CONFORMING TO
+This type is Linux-specific.
+.SH SEE ALSO
+.BR openat2 (2)