From: Aleksa Sarai <cyphar@cyphar.com>
To: mtk.manpages@gmail.com
Cc: Aleksa Sarai <cyphar@cyphar.com>,
Thadeu Lima de Souza Cascardo <cascardo@canonical.com>,
Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Jiri Olsa <jolsa@redhat.com>,
Patrick Bellasi <patrick.bellasi@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-man@vger.kernel.org, linux-api@vger.kernel.org
Subject: [PATCH 2/2] openat2.2: fix minor reference typo
Date: Wed, 30 Sep 2020 08:35:09 +1000 [thread overview]
Message-ID: <20200929223509.11783-2-cyphar@cyphar.com> (raw)
In-Reply-To: <20200929223509.11783-1-cyphar@cyphar.com>
Signed-off-by: Aleksa Sarai <cyphar@cyphar.com>
---
man2/openat2.2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man2/openat2.2 b/man2/openat2.2
index 29b716d97ac4..53056ee6d292 100644
--- a/man2/openat2.2
+++ b/man2/openat2.2
@@ -493,7 +493,7 @@ acting as an implicit version number.
(Because new extension fields will always
be appended, the structure size will always increase.)
This extensibility design is very similar to other system calls such as
-.BR perf_setattr (2),
+.BR sched_setattr (2),
.BR perf_event_open (2),
and
.BR clone3 (2).
--
2.28.0
next prev parent reply other threads:[~2020-09-29 22:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 12:01 [PATCH] sched_getattr.2: update to include changed size semantics Aleksa Sarai
2019-11-28 13:08 ` Thadeu Lima de Souza Cascardo
2019-11-28 13:55 ` Aleksa Sarai
2020-04-25 19:12 ` Michael Kerrisk (man-pages)
2020-05-15 12:10 ` Michael Kerrisk (man-pages)
2020-09-29 22:35 ` [PATCH 1/2] " Aleksa Sarai
2020-09-29 22:35 ` Aleksa Sarai [this message]
2020-09-30 10:51 ` [PATCH 2/2] openat2.2: fix minor reference typo Michael Kerrisk (man-pages)
2020-09-30 10:51 ` [PATCH 1/2] sched_getattr.2: update to include changed size semantics 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=20200929223509.11783-2-cyphar@cyphar.com \
--to=cyphar@cyphar.com \
--cc=acme@infradead.org \
--cc=cascardo@canonical.com \
--cc=jolsa@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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).