From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Rong Xu <xur@google.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Klara Modin <klarasmodin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicolas Schier <nicolas@fjasle.eu>,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
Sergey Shtylyov <s.shtylyov@omp.ru>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MIPS: Add a blank line after __HEAD
Date: Sat, 11 Jan 2025 13:04:18 +0100 [thread overview]
Message-ID: <Z4JeQlQGJpyuJmM9@alpha.franken.de> (raw)
In-Reply-To: <20241203173431.3790387-1-xur@google.com>
On Tue, Dec 03, 2024 at 09:34:31AM -0800, Rong Xu wrote:
> Add a blank line after __HEAD in the text section.
>
> The __HEAD symbol was added in commit 52892ed6b03a ("MIPS:
> Place __kernel_entry at the beginning of text section").
>
> Signed-off-by: Rong Xu <xur@google.com>
> Suggested-by: Maciej W. Rozycki <macro@orcam.me.uk>
>
> ---Changelog--
> Added suggested-by.
> ---
> arch/mips/kernel/head.S | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/mips/kernel/head.S b/arch/mips/kernel/head.S
> index e3ff6179c99f9..d99ed58b7043d 100644
> --- a/arch/mips/kernel/head.S
> +++ b/arch/mips/kernel/head.S
> @@ -60,6 +60,7 @@
> .endm
>
> __HEAD
> +
> #ifndef CONFIG_NO_EXCEPT_FILL
> /*
> * Reserved space for exception handlers.
>
> base-commit: e70140ba0d2b1a30467d4af6bcfe761327b9ec95
> --
> 2.47.0.338.g60cca15819-goog
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2025-01-11 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 17:34 Rong Xu
2025-01-11 12:04 ` Thomas Bogendoerfer [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=Z4JeQlQGJpyuJmM9@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=christophe.leroy@csgroup.eu \
--cc=klarasmodin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=masahiroy@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=nicolas@fjasle.eu \
--cc=s.shtylyov@omp.ru \
--cc=xur@google.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®