From: walter harms <wharms@bfs.de>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Adam Borowski <kilobyte@angband.pl>,
Florin Blanaru <florin.blanaru96@gmail.com>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: Quick fix for syscall man page
Date: Tue, 10 Sep 2019 12:45:52 +0200 [thread overview]
Message-ID: <5D777EE0.6030906@bfs.de> (raw)
In-Reply-To: <6da7ef65-c9aa-b670-7305-25c7f4e9f9f8@gmail.com>
Am 10.09.2019 10:26, schrieb Michael Kerrisk (man-pages):
> Hello Adam,
>
> Thanks for jumping in.
> On 9/9/19 8:27 PM, Adam Borowski wrote:
>> On Mon, Sep 09, 2019 at 11:08:34AM +0200, walter harms wrote:
>>> Am 09.09.2019 10:52, schrieb Michael Kerrisk (man-pages):
>>>> [Adding Adam Borowski in CC, since he wrote the riscv text back at the
>>>> start of 2018, andand he may have a comment.]
>>
>> I don't know RISCV; I needed to learn how to issue syscalls to port
>> something -- so I've searched for relevant documentation, tested that it
>> indeed works, then submitted that line to make the man page complete.
>>
>>>> On Thu, 5 Sep 2019 at 18:35, Florin Blanaru <florin.blanaru96@gmail.com> wrote:
>>>>> 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
>>
>> What matters for us, and the vast majority of programmers, is that the
>> rename predates merging into official releases of binutils. Thus, there is
>> no reason to ever use the old name in actual code.
>>
>>> Maybe it would be helpful to add a "footnote" that this is a rename only.
>>> Otherwise people may get confused.
>>
>> I wonder, perhaps just a commit message would be enough? The alias is
>> historic only; new documentation is supposed to use the new name. Man pages
>> contain a lot of data that has been obsolete for decades -- it might be good
>> to avoid stuff that became obsolete before the official release.
>>
>> But it's up to you -- you know better what's your policy about historical
>> information.
>
> On reflection, I agree. I'll trim this back to a note in the commit
> message only. (Nevertheless, thanks, Walter.)
>
Just my view on this:
most people that work on this level may know about that. NTL they also
tend to stick what worked last time. IMHO is the note important since
this is a naming only, you look at the man page not at the archive when
you are in doubt.
Something like: "In 2017 scall war renamed as ecall" is a harmless note.
note; i am not a risc programmer. it is just a general concern.
re,
wh
> Cheers,
>
> Michael
>
>>>> --- a/man2/syscall.2
>>>> +++ b/man2/syscall.2
>>>> @@ -196,7 +196,7 @@ mips syscall v0 v0 v1 a3 1, 6
>>>> -riscv scall a7 a0 a1 -
>>>> +riscv ecall a7 a0 a1 -
>>
>>
>> Meow!
>>
>
>
prev parent reply other threads:[~2019-09-10 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 16:34 Quick fix for syscall man page Florin Blanaru
2019-09-09 8:52 ` 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 [this message]
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=5D777EE0.6030906@bfs.de \
--to=wharms@bfs.de \
--cc=florin.blanaru96@gmail.com \
--cc=kilobyte@angband.pl \
--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 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.