From: Palmer Dabbelt <palmer@dabbelt.com>
To: georgedanielmangum@gmail.com
Cc: georgedanielmangum@gmail.com,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, alex@ghiti.fr, vitaly.wool@konsulko.com,
anup@brainfault.org, mark.rutland@arm.com, ardb@kernel.org,
181250012@smail.nju.edu.cn, wangkefeng.wang@huawei.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv/head: fix misspelling of guaranteed
Date: Fri, 07 Jan 2022 11:18:04 -0800 (PST) [thread overview]
Message-ID: <mhng-047fcd51-673f-4bb7-a19f-beecd00667e8@palmer-ri-x1c9> (raw)
In-Reply-To: <20211120142608.2068809-1-georgedanielmangum@gmail.com>
On Sat, 20 Nov 2021 06:26:05 PST (-0800), georgedanielmangum@gmail.com wrote:
> Fixes misspelling of guaranteed in comment describing why fetching fence
> is guaranteed to work when switching to kernel page tables.
>
> Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
> ---
> arch/riscv/kernel/head.S | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/riscv/kernel/head.S b/arch/riscv/kernel/head.S
> index f52f01ecbeea..469eccd3780f 100644
> --- a/arch/riscv/kernel/head.S
> +++ b/arch/riscv/kernel/head.S
> @@ -135,7 +135,7 @@ relocate:
> /*
> * Switch to kernel page tables. A full fence is necessary in order to
> * avoid using the trampoline translations, which are only correct for
> - * the first superpage. Fetching the fence is guarnteed to work
> + * the first superpage. Fetching the fence is guaranteed to work
> * because that first superpage is translated the same way.
> */
> csrw CSR_SATP, a2
Thanks, this is on for-next.
prev parent reply other threads:[~2022-01-07 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 14:26 [PATCH] riscv/head: fix misspelling of guaranteed hasheddan
2022-01-07 19:18 ` Palmer Dabbelt [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=mhng-047fcd51-673f-4bb7-a19f-beecd00667e8@palmer-ri-x1c9 \
--to=palmer@dabbelt.com \
--cc=181250012@smail.nju.edu.cn \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=georgedanielmangum@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=paul.walmsley@sifive.com \
--cc=vitaly.wool@konsulko.com \
--cc=wangkefeng.wang@huawei.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;
as well as URLs for NNTP newsgroup(s).