From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page __riscv_flush_icache.3
Date: Fri, 26 Dec 2025 11:46:30 +0100 [thread overview]
Message-ID: <aU5m0sSpRclqY4Pi@devuan> (raw)
In-Reply-To: <aU4VGitTZacSjEht@meinfjell.helgefjelltest.de>
[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]
Hi Helge,
On Fri, Dec 26, 2025 at 04:54:50AM +0000, Helge Kreutzmann wrote:
> Hello Alex,
> Am Thu, Dec 25, 2025 at 02:34:48PM +0100 schrieb Alejandro Colomar:
> > On Wed, Dec 24, 2025 at 02:38:24PM +0000, Helge Kreutzmann wrote:
> > > Without further ado, the following was found:
> > >
> > > Issue: flag bits → I<flag> bits
> >
> > The parameter is 'flags', not 'flag'. Thus, 'flag' can only be the
> > English word, and thus not be in italics. The text is correct.
>
>
> > > "The I<flags> argument controls the extent of this ordering, with the default "
> > > "behavior (a I<flags> value of 0) being to enforce the fence on all threads "
> > > "in the current process. Setting the B<SYS_RISCV_FLUSH_ICACHE_LOCAL> bit "
> > > "allows users to indicate that enforcing ordering on only the current thread "
> > > "is necessary. All other flag bits are reserved."
>
> So this is not referring to the variable <flags>?
>
> (Yes, I forgot to add the "s" myself).
>
> If it does refer to this variable you might resolve this by rewording:
>
> All other bits stored in the argument I<flags> are reserved.
Yes, that would be appropriate, and would help the reader. I'll change
it. Thanks for the suggestion!
> Btw. in the German translations team there used to be some discussions
> if you could switch (add/remove) a genetiv or plural "s" to suite the
> the grammar.
I would never change the spelling of an identifier used in code. I'd
certainly never remove it. If you add it, at least the plural should
not be in italics, so that the identifier can still be identified.
Have a lovely day!
Alex
> Greetings
>
> Helge
>
> --
> Dr. Helge Kreutzmann debian@helgefjell.de
> Dipl.-Phys. http://www.helgefjell.de/debian.php
> 64bit GNU powered gpg signed mail preferred
> Help keep free software "libre": http://www.ffii.de/
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-26 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 14:38 Issue in man page __riscv_flush_icache.3 Helge Kreutzmann
2025-12-25 13:34 ` Alejandro Colomar
2025-12-26 4:54 ` Helge Kreutzmann
2025-12-26 10:46 ` Alejandro Colomar [this message]
2025-12-26 11:14 ` Helge Kreutzmann
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=aU5m0sSpRclqY4Pi@devuan \
--to=alx@kernel.org \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@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