From: Paul Walmsley <pjw@kernel.org>
To: Kunwu Chan <kunwu.chan@linux.dev>
Cc: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Conor Dooley <conor@kernel.org>, Alexandre Ghiti <alex@ghiti.fr>,
Anup Patel <anup@brainfault.org>,
Atish Patra <atishp@rivosinc.com>, Zong Li <zong.li@sifive.com>,
Deepak Gupta <debug@rivosinc.com>,
Zhouyi Zhou <zhouzhouyi@gmail.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 0/2] riscv: fix minor typos and style issues in XIP code
Date: Wed, 18 Mar 2026 17:23:48 -0600 (MDT) [thread overview]
Message-ID: <26ca22b1-b6d6-a733-2ab0-7fc83908bec0@kernel.org> (raw)
In-Reply-To: <20260214023804.677127-1-kunwu.chan@linux.dev>
Hi,
On Sat, 14 Feb 2026, Kunwu Chan wrote:
> Fix a few minor issues found in riscv XIP-related code:
>
> - xip_fixup.h: comment typo (_start vs _sdata) and spaces-vs-tab
> - head.S: spelling typo and wrong #endif comment
>
> Kunwu Chan (2):
> riscv: xip_fixup.h: fix comment typo and whitespace issue
> riscv: head.S: fix typo and wrong #endif comment
>
> arch/riscv/include/asm/xip_fixup.h | 4 ++--
> arch/riscv/kernel/head.S | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
Please see:
https://lore.kernel.org/linux-riscv/609b889a-8bb1-d2b5-8de6-ddeec27cac04@kernel.org/
- Paul
prev parent reply other threads:[~2026-03-18 23:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 2:38 Kunwu Chan
2026-02-14 2:38 ` [PATCH RESEND 1/2] riscv: xip_fixup.h: fix comment typo and whitespace issue Kunwu Chan
2026-02-14 2:38 ` [PATCH RESEND 2/2] riscv: head.S: fix typo and wrong #endif comment Kunwu Chan
2026-02-17 21:12 ` [PATCH RESEND 0/2] riscv: fix minor typos and style issues in XIP code Paul Walmsley
2026-02-18 0:58 ` Nam Cao
2026-02-20 15:38 ` Jisheng Zhang
2026-02-20 22:39 ` Conor Dooley
2026-03-18 23:23 ` Paul Walmsley [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=26ca22b1-b6d6-a733-2ab0-7fc83908bec0@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=conor@kernel.org \
--cc=debug@rivosinc.com \
--cc=kunwu.chan@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=zhouzhouyi@gmail.com \
--cc=zong.li@sifive.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
Powered by JetHome