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 PR_RISCV_SET_ICACHE_FLUSH_CTX.2const
Date: Thu, 25 Dec 2025 22:03:25 +0100 [thread overview]
Message-ID: <aU2lzU_5FB94Yqf6@devuan> (raw)
In-Reply-To: <aUv63mfzFe9WIr4z@meinfjell.helgefjelltest.de>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
Hi Helge,
On Wed, Dec 24, 2025 at 02:38:22PM +0000, Helge Kreutzmann wrote:
> Without further ado, the following was found:
>
> Issue 1: modify_instruction() → B<modify_instruction()>
> Issue 2: get_value() → B<get_value()>
>
> "The following files are meant to be compiled and linked with each other. "
> "The modify_instruction() function replaces an add with zero with an add with "
> "one, causing the instruction sequence in get_value() to change from "
> "returning a zero to returning a one."
Since these functions are just part of this example, and not something
standard nor provided by any library nor documented anywhere, I think we
shouldn't mark them up.
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-25 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 14:38 Issue in man page PR_RISCV_SET_ICACHE_FLUSH_CTX.2const Helge Kreutzmann
2025-12-25 21:03 ` Alejandro Colomar [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-24 14:38 Helge Kreutzmann
2025-12-25 21:06 ` Alejandro Colomar
2025-12-24 14:38 Helge Kreutzmann
2025-12-24 14:38 Helge Kreutzmann
2025-12-24 15:52 ` Alejandro Colomar
2025-12-24 14:38 Helge Kreutzmann
2025-12-24 14:38 Helge Kreutzmann
2025-12-25 13:59 ` Alejandro Colomar
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=aU2lzU_5FB94Yqf6@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