From: Andreas Schwab <schwab@linux-m68k.org>
To: Florian Wagner <florian.wagner@nextsilicon.com>
Cc: paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
yaron.dinkin@nextsilicon.com
Subject: Re: [PATCH 1/1] RISC-V: Change signature header field to use `.ascii` instead of opcode
Date: Mon, 17 Jan 2022 19:44:54 +0100 [thread overview]
Message-ID: <878rve6w2h.fsf@igel.home> (raw)
In-Reply-To: <20220117173941.3798325-2-florian.wagner@nextsilicon.com> (Florian Wagner's message of "Mon, 17 Jan 2022 18:39:41 +0100")
On Jan 17 2022, Florian Wagner wrote:
> diff --git a/arch/riscv/kernel/head.S b/arch/riscv/kernel/head.S
> index f52f01ecbeea..931b63464b90 100644
> --- a/arch/riscv/kernel/head.S
> +++ b/arch/riscv/kernel/head.S
> @@ -48,7 +48,7 @@ ENTRY(_start)
> /*
> * This instruction decodes to "MZ" ASCII required by UEFI.
> */
> - c.li s4,-13
> + .ascii "MZ"
The comment above no longer makes sense.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-01-17 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 17:39 [PATCH 0/1] RISC-V: Make stub compile without c extension Florian Wagner
2022-01-17 17:39 ` [PATCH 1/1] RISC-V: Change signature header field to use `.ascii` instead of opcode Florian Wagner
2022-01-17 18:44 ` Andreas Schwab [this message]
2022-01-17 18:59 ` Jessica Clarke
2022-01-18 1:23 ` Kefeng Wang
2022-01-18 1:25 ` Atish Patra
2022-01-20 19:06 ` Palmer Dabbelt
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=878rve6w2h.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=aou@eecs.berkeley.edu \
--cc=florian.wagner@nextsilicon.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=yaron.dinkin@nextsilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.