Linux Manual Pages development
 help / color / mirror / Atom feed
From: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH draft_keys 3/7] keyrings.7: spacing fix
Date: Fri, 25 Nov 2016 04:01:04 +0300	[thread overview]
Message-ID: <20161125010104.GA453@obsidian> (raw)
In-Reply-To: <51643019-bb42-4066-c824-c55b9e668ac6-ASgREoAs3yw@public.gmane.org>

---
 man7/keyrings.7 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man7/keyrings.7 b/man7/keyrings.7
index ed3bbee..c15a273 100644
--- a/man7/keyrings.7
+++ b/man7/keyrings.7
@@ -145,7 +145,7 @@ that should not be readable from user space.
 .\" commit ab3c3587f8cda9083209a61dbe3a4407d3cada10
 This key type is similar to the
 .I """user"""
-key type, but it may hold a payload of up to 1MiB in size.
+key type, but it may hold a payload of up to 1 MiB in size.
 The data may be stored in the swap space rather than in kernel memory
 if the data size exceeds the overhead of storing the data in swap space
 (a tmpfs file is used, which requires filesystem structures
-- 
2.10.2

--
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

  parent reply	other threads:[~2016-11-25  1:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 15:47 Revised keyrings(7) man page for review Michael Kerrisk
     [not found] ` <51643019-bb42-4066-c824-c55b9e668ac6-ASgREoAs3yw@public.gmane.org>
2016-11-25  1:00   ` [PATCH draft_keys 0/7] Minor edits Eugene Syromyatnikov
2016-11-25 10:01     ` Michael Kerrisk (man-pages)
2016-11-25  1:00   ` [PATCH draft_keys 1/7] keyctl.2: tfix Eugene Syromyatnikov
2016-11-25  8:35     ` Michael Kerrisk (man-pages)
2016-11-25  1:00   ` [PATCH draft_keys 2/7] keyrings.7: minor clarification rearding storage method used in keyrings Eugene Syromyatnikov
2016-11-25  8:37     ` Michael Kerrisk (man-pages)
2016-11-25  1:01   ` Eugene Syromyatnikov [this message]
2016-11-25  8:39     ` [PATCH draft_keys 3/7] keyrings.7: spacing fix Michael Kerrisk (man-pages)
2016-11-25  1:01   ` [PATCH draft_keys 4/7] keyrings.7: minor clarification regarding decision whether to store big_key in tmpfs or not Eugene Syromyatnikov
2016-11-25  8:40     ` Michael Kerrisk (man-pages)
2016-11-25  1:01   ` [PATCH draft_keys 5/7] keyrings.7: tfix Eugene Syromyatnikov
2016-11-25  8:42     ` Michael Kerrisk (man-pages)
2016-11-25  1:01   ` [PATCH draft_keys 6/7] " Eugene Syromyatnikov
2016-11-25  8:43     ` Michael Kerrisk (man-pages)
2016-11-25  1:01   ` [PATCH draft_keys 7/7] keyrings.7: information regarding pre-3.17 limits on root_maxbytes/root_maxkeys Eugene Syromyatnikov
2016-11-25  8:54     ` Michael Kerrisk (man-pages)
2016-11-26 12:51   ` Revised keyrings(7) man page for review Michael Kerrisk (man-pages)
2016-12-13 11:35   ` David Howells
     [not found]     ` <25262.1481628931-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2016-12-13 12:43       ` Michael Kerrisk (man-pages)
     [not found]         ` <9f32a79b-5795-bff4-b741-bf927a525149-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-13 12:57           ` Michael Kerrisk (man-pages)
2016-12-13 13:31         ` David Howells
2016-12-13 13:41           ` Michael Kerrisk (man-pages)
     [not found]         ` <CAKgNAkh9JLN4P+Fu+yRCNo96E3VwjYLRquuaf43XRWeuC7gnNw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-13 13:38           ` David Howells
     [not found]             ` <26913.1481636296-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2016-12-13 13:52               ` Michael Kerrisk (man-pages)
     [not found]             ` <a5615075-dd39-e206-cbce-385bed72473f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-13 14:20               ` David Howells
2016-12-14  7:27                 ` 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=20161125010104.GA453@obsidian \
    --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