From: Kunwu Chan <kunwu.chan@linux.dev>
To: Conor Dooley <conor@kernel.org>
Cc: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
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>,
zhouzhouyi <zhouzhouyi@gmail.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] riscv: fix minor typos and style issues in XIP code
Date: Sat, 14 Feb 2026 10:25:57 +0800 [thread overview]
Message-ID: <8ee1b065-b021-411b-b5ee-22c4a108cbce@linux.dev> (raw)
In-Reply-To: <20260213-entomb-ambulance-ec51cd9ea179@spud>
On 2/13/26 18:47, Conor Dooley wrote:
> On Fri, Feb 13, 2026 at 05:47:37PM +0800, 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(-)
> The patches should be sent in reply to the cover letter.
Thanks. I'll resend the series properly threaded.
--
Thanx, Kunwu
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-02-14 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 9:47 [PATCH 0/2] riscv: fix minor typos and style issues in XIP code Kunwu Chan
2026-02-13 10:47 ` Conor Dooley
2026-02-14 2:25 ` Kunwu Chan [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=8ee1b065-b021-411b-b5ee-22c4a108cbce@linux.dev \
--to=kunwu.chan@linux.dev \
--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=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--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