From: Andy Lutomirski <luto@amacapital.net>
To: Michael Kerrisk <mtk.manpages@gmail.com>, linux-kernel@vger.kernel.org
Cc: Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH manpages 0/2] Improve modify_ldt, [gs]et_thread_area docs
Date: Thu, 29 Jan 2015 13:47:53 -0800 [thread overview]
Message-ID: <cover.1422568013.git.luto@amacapital.net> (raw)
The docs for set_thread_area, get_thread_area, and modify_ldt are pretty
bad, and there have been a number of kernel changes lately. Improve
and update the docs.
Andy Lutomirski (2):
modify_ldt.2: Overhaul the documentation
arch_prctl.2, set_thread_area.2, get_thread_area.2: Improve TLS
documentation
man2/arch_prctl.2 | 22 +++++++----
man2/get_thread_area.2 | 58 +---------------------------
man2/modify_ldt.2 | 101 ++++++++++++++++++++++++++++++++++++++-----------
man2/set_thread_area.2 | 93 ++++++++++++++++++++++++++++++++++++++++++---
4 files changed, 180 insertions(+), 94 deletions(-)
--
2.1.0
next reply other threads:[~2015-01-29 21:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 21:47 Andy Lutomirski [this message]
2015-01-29 21:47 ` [PATCH manpages 1/2] modify_ldt.2: Overhaul the documentation Andy Lutomirski
2015-01-30 12:18 ` Michael Kerrisk (man-pages)
2015-01-30 14:42 ` Andy Lutomirski
2015-01-30 15:21 ` Michael Kerrisk (man-pages)
2015-01-29 21:47 ` [PATCH manpages 2/2] arch_prctl.2, set_thread_area.2, get_thread_area.2: Improve TLS documentation Andy Lutomirski
[not found] ` <eea75b78032d04f45ba1f33626b26f6b4f5c8ca3.1422568013.git.luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>
2015-01-30 12:59 ` Michael Kerrisk (man-pages)
2015-01-30 12:59 ` Michael Kerrisk (man-pages)
2015-01-30 14:45 ` Andy Lutomirski
[not found] ` <CALCETrXK+GRN2uhfJJcYcbO1T3mruRyer3XMCYYJGNkinCjwbA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-30 15:18 ` Michael Kerrisk (man-pages)
2015-01-30 15:18 ` Michael Kerrisk (man-pages)
2015-01-30 12:18 ` [PATCH manpages 0/2] Improve modify_ldt, [gs]et_thread_area docs Michael Kerrisk (man-pages)
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=cover.1422568013.git.luto@amacapital.net \
--to=luto@amacapital.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.