From: Randy Dunlap <rdunlap@infradead.org>
To: ChunyouTang <tangchunyou@163.com>,
ink@jurassic.park.msu.ru, mattst88@gmail.com,
akpm@linux-foundation.org, rppt@kernel.org
Cc: linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
zhangwen@yulong.com, tangchunyou@yulong.com
Subject: Re: [PATCH] arch/alpha: fix typo in a comment in arch/alpha/boot/bootpz.c
Date: Wed, 20 Jan 2021 08:20:09 -0800 [thread overview]
Message-ID: <5e4ed85d-140c-3d85-e4f4-97b27fa37885@infradead.org> (raw)
In-Reply-To: <20210120133410.2182-1-tangchunyou@163.com>
On 1/20/21 5:34 AM, ChunyouTang wrote:
> From: tangchunyou <tangchunyou@yulong.com>
>
> "kerne" -> "kernel"
>
> Signed-off-by: tangchunyou <tangchunyou@yulong.com>
> ---
> arch/alpha/boot/bootpz.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/alpha/boot/bootpz.c b/arch/alpha/boot/bootpz.c
> index 43af718..61b61be 100644
> --- a/arch/alpha/boot/bootpz.c
> +++ b/arch/alpha/boot/bootpz.c
> @@ -200,7 +200,7 @@ extern int decompress_kernel(void* destination, void *source,
> START_ADDR KSEG address of the entry point of kernel code.
>
> ZERO_PGE KSEG address of page full of zeroes, but
> - upon entry to kerne cvan be expected
> + upon entry to kernel cvan be expected
s/cvan/can/ also
> to hold the parameter list and possible
> INTRD information.
>
>
--
~Randy
"He closes his eyes and drops the goggles. You can't get hurt
by looking at a bitmap. Or can you?"
(Neal Stephenson: Snow Crash)
next prev parent reply other threads:[~2021-01-20 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 13:34 ChunyouTang
2021-01-20 16:20 ` John Paul Adrian Glaubitz
2021-01-20 16:20 ` Randy Dunlap [this message]
2021-01-20 16:37 ` John Paul Adrian Glaubitz
2021-01-21 2:20 ` Chunyou Tang
2021-01-21 8:00 ` John Paul Adrian Glaubitz
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=5e4ed85d-140c-3d85-e4f4-97b27fa37885@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=rppt@kernel.org \
--cc=tangchunyou@163.com \
--cc=tangchunyou@yulong.com \
--cc=zhangwen@yulong.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
all inboxes | Powered by JetHome®