From: Florin Blanaru <florin.blanaru96@gmail.com>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org
Subject: Quick fix for syscall man page
Date: Thu, 5 Sep 2019 17:34:54 +0100 [thread overview]
Message-ID: <CAMkHNDzkn10oZLyK9S8-UnjGn=OyMy=P8Bx7+vf0iEBwpc5p2g@mail.gmail.com> (raw)
http://man7.org/linux/man-pages/man2/syscall.2.html
In the first table, for the riscv Arch/ABI, the instruction should be
ecall instead of scall.
According the official manual, the instruction has been renamed.
https://content.riscv.org/wp-content/uploads/2017/05/riscv-spec-v2.2.pdf
"The SCALL and SBREAK instructions have been renamed to ECALL and
EBREAK, re-spectively. Their encoding and functionality are
unchanged."
next reply other threads:[~2019-09-05 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 16:34 Florin Blanaru [this message]
2019-09-09 8:52 ` Quick fix for syscall man page Michael Kerrisk (man-pages)
2019-09-09 9:08 ` walter harms
2019-09-09 12:42 ` Michael Kerrisk (man-pages)
2019-09-09 18:27 ` Adam Borowski
2019-09-10 8:26 ` Michael Kerrisk (man-pages)
2019-09-10 10:45 ` walter harms
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='CAMkHNDzkn10oZLyK9S8-UnjGn=OyMy=P8Bx7+vf0iEBwpc5p2g@mail.gmail.com' \
--to=florin.blanaru96@gmail.com \
--cc=linux-man@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 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).