From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, schwab@linux-m68k.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -fixes] riscv: Fix relocatable kernels with early alternatives using -fno-pie
Date: Wed, 31 May 2023 15:10:21 +0000 [thread overview]
Message-ID: <168554582178.8247.10623595249995347296.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230526154630.289374-1-alexghiti@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 26 May 2023 17:46:30 +0200 you wrote:
> Early alternatives are called with the mmu disabled, and then should not
> access any global symbols through the GOT since it requires relocations,
> relocations that we do before but *virtually*. So only use medany code
> model for this early code.
>
> Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
>
> [...]
Here is the summary with links:
- [-fixes] riscv: Fix relocatable kernels with early alternatives using -fno-pie
https://git.kernel.org/riscv/c/8dc2a7e8027f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-05-31 15:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 15:46 [PATCH -fixes] riscv: Fix relocatable kernels with early alternatives using -fno-pie Alexandre Ghiti
2023-05-26 16:24 ` Conor Dooley
2023-05-26 16:35 ` Conor Dooley
2023-05-27 9:13 ` Alexandre Ghiti
2023-05-27 10:02 ` Conor Dooley
2023-05-28 13:00 ` Alexandre Ghiti
2023-05-28 13:12 ` Conor Dooley
2023-05-28 13:42 ` Alexandre Ghiti
2023-05-28 13:56 ` Conor Dooley
2023-05-29 18:51 ` Alexandre Ghiti
2023-05-29 19:06 ` Conor Dooley
2023-05-29 19:37 ` Alexandre Ghiti
2023-05-30 11:27 ` Conor Dooley
2023-05-30 14:33 ` Alexandre Ghiti
2023-05-30 17:47 ` Conor Dooley
2023-05-30 18:04 ` Alexandre Ghiti
2023-05-30 20:22 ` Conor Dooley
2023-05-31 7:26 ` Alexandre Ghiti
2023-05-31 9:32 ` Conor Dooley
2023-05-31 11:03 ` Alexandre Ghiti
2023-05-26 16:38 ` Alexandre Ghiti
2023-05-31 15:03 ` Palmer Dabbelt
2023-05-31 15:10 ` patchwork-bot+linux-riscv [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=168554582178.8247.10623595249995347296.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=schwab@linux-m68k.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