From: "Heiko Stübner" <heiko@sntech.de>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Guo Ren <guoren@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Icenowy Zheng <uwu@icenowy.me>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 2/2] riscv: errata: prefix T-Head mnemonics with th.
Date: Tue, 03 Jan 2023 09:35:01 +0100 [thread overview]
Message-ID: <5641668.DvuYhMxLoT@diego> (raw)
In-Reply-To: <20230103062610.69704-2-uwu@icenowy.me>
Am Dienstag, 3. Januar 2023, 07:26:10 CET schrieb Icenowy Zheng:
> T-Head now maintains some specification for their extended instructions
> at [1], in which all instructions are prefixed "th.".
>
> Follow this practice in the kernel comments.
>
> [1] https://github.com/T-head-Semi/thead-extension-spec
>
> Signed-off-by: Icenowy Zheng <uwu@icenowy.me>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-01-03 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 6:26 [PATCH RESEND 1/2] riscv: errata: fix T-Head dcache.cva encoding Icenowy Zheng
2023-01-03 6:26 ` [PATCH RESEND 2/2] riscv: errata: prefix T-Head mnemonics with th Icenowy Zheng
2023-01-03 8:35 ` Heiko Stübner [this message]
2023-01-03 10:18 ` Conor Dooley
2023-01-03 19:10 ` Conor Dooley
2023-01-03 8:34 ` [PATCH RESEND 1/2] riscv: errata: fix T-Head dcache.cva encoding Heiko Stübner
2023-01-03 12:02 ` Guo Ren
2023-01-24 13:19 ` Icenowy Zheng
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=5641668.DvuYhMxLoT@diego \
--to=heiko@sntech.de \
--cc=aou@eecs.berkeley.edu \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nathan@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=uwu@icenowy.me \
/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