From: Sean Chang <seanwascoding@gmail.com>
To: conor@kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-riscv@lists.infradead.org,
palmer@dabbelt.com, pjw@kernel.org, seanwascoding@gmail.com
Subject: Re: [PATCH v2] riscv: fix typos in comments/code - CC Conor
Date: Thu, 12 Feb 2026 22:47:12 +0800 [thread overview]
Message-ID: <20260212144712.15690-1-seanwascoding@gmail.com> (raw)
In-Reply-To: <20260211-trash-eldest-aebdecd512c4@spud>
Hi Conor,
Thanks for quick feedback on v1!
Fixed your comments:
- elf.h: coorespends → corresponds
- processor.h: requries → is required
v2 here: https://lore.kernel.org/linux-riscv/20260211175429.94329-1-seanwascoding@gmail.com/
Please review!
Thanks,
Sean
---
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-02-12 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 16:58 [PATCH] riscv: fix various typos in comments and code seanwascoding
2026-02-11 17:05 ` Conor Dooley
2026-02-12 14:47 ` Sean Chang [this message]
2026-02-11 17:54 ` [PATCH v2] " Sean Chang
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=20260212144712.15690-1-seanwascoding@gmail.com \
--to=seanwascoding@gmail.com \
--cc=conor@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
/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