From: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 1/3] adjtimex.2: tfix
Date: Sun, 13 Mar 2016 19:00:57 +0100 [thread overview]
Message-ID: <1457892059-7685-1-git-send-email-jwilk@jwilk.net> (raw)
Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
---
man2/adjtimex.2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man2/adjtimex.2 b/man2/adjtimex.2
index 324de05..adcfbca 100644
--- a/man2/adjtimex.2
+++ b/man2/adjtimex.2
@@ -456,7 +456,7 @@ does not point to writable memory.
An attempt was made to set
.I buf.freq
to a value outside the range (\-33554432, +33554432).
-.\" From a quck glance, it appears there was no clamping or range check
+.\" From a quick glance, it appears there was no clamping or range check
.\" for buf.freq in kernels before 2.0
.TP
.BR EINVAL " (kernels before Linux 2.6.26)"
--
2.7.0
--
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:[~2016-03-13 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 18:00 Jakub Wilk [this message]
[not found] ` <1457892059-7685-1-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2016-03-13 18:00 ` [PATCH 2/3] readdir_r.3: tfix Jakub Wilk
[not found] ` <1457892059-7685-2-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2016-03-13 19:34 ` Michael Kerrisk (man-pages)
2016-03-13 18:00 ` [PATCH 3/3] feature_test_macros.7: tfix Jakub Wilk
[not found] ` <1457892059-7685-3-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2016-03-13 19:34 ` Michael Kerrisk (man-pages)
2016-03-13 19:34 ` [PATCH 1/3] adjtimex.2: tfix 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=1457892059-7685-1-git-send-email-jwilk@jwilk.net \
--to=jwilk-txgolizoknreowh0uzbu5w@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;
as well as URLs for NNTP newsgroup(s).