From: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 00/15] Updates of in-kernel documentation pointers
Date: Mon, 11 Sep 2017 05:03:47 +0200 [thread overview]
Message-ID: <20170911030347.GA24854@asgard.redhat.com> (raw)
Hello.
I've noticed that some of Linux kernel in-tree documentation pointers
are no longer valid and decided to check the validity for the rest of
them with some one-liner. As it turned out, there are quite a few of
them, in part due to latest ReST conversion effort. This patch set aims
at amending documentation pointers that are no longer valid with the
information about current location. I'm not quite sure about
wording/formatting, and do not guarantee that I haven't miss anything,
so I hope that this could be at least useful as a starting point.
Eugene Syromyatnikov (15):
add_key.2, request_key.2, keyrings.7: update Linux documentation
pointers
prctl.2, ptrace.2: update pointer to in-kernel Yama documentation
prctl.2: update pointer to in-kernel no_new_privs flag documentation
prctl.2, seccomp.2: update pointer to in-kernel seccomp documentation
unshare.2: update pointer to in-kernel unshare documentation
initrd.4: update pointer to in-kernel root over NFS documentation
initrd.4, proc.5, bootparam.7: update pointer to in-kernel initrd
documentation
proc.5: document removal of htab-reclaim sysctl file
proc.5: document removal of timer_stats file
proc.5: update pointer to in-kernel security keys documentation
proc.5: update reference to kernel's crypto API documentation
proc.5: update pointer to in-kernel MTRR documentation
proc.5: update pointer to in-kernel SysRq documentation
cpuset.7: update pointer to in-kernel cpusets documentation
unicode.7: update pointer to in-kernel Unicode terminal support
documentation
man2/add_key.2 | 8 +++++++-
man2/prctl.2 | 18 +++++++++++++++---
man2/ptrace.2 | 4 ++++
man2/request_key.2 | 8 +++++++-
man2/seccomp.2 | 6 +++++-
man2/unshare.2 | 6 +++++-
man4/initrd.4 | 14 +++++++++++++-
man5/proc.5 | 54 ++++++++++++++++++++++++++++++++++++++++++++----------
man7/bootparam.7 | 6 +++++-
man7/cpuset.7 | 6 +++++-
man7/keyrings.7 | 4 +++-
man7/unicode.7 | 6 +++++-
12 files changed, 118 insertions(+), 22 deletions(-)
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-09-11 3:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 3:03 Eugene Syromyatnikov [this message]
[not found] ` <20170911030347.GA24854-ZbobWygYI+YXGNroddHbYwC/G2K4zDHf@public.gmane.org>
2017-09-11 11:47 ` [PATCH 00/15] Updates of in-kernel documentation pointers Christoph Hellwig
[not found] ` <20170911114747.GA3463-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-09-11 11:56 ` Eugene Syromyatnikov
2017-09-11 13:54 ` Michael Kerrisk (man-opages)
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=20170911030347.GA24854@asgard.redhat.com \
--to=evgsyr-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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