From: patchwork-bot+linux-riscv@kernel.org
To: Vladimir Isaev <vladimir.isaev@syntacore.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
catalin.marinas@arm.com, evan@rivosinc.com, nicolas@fjasle.eu,
tglx@linutronix.de, samitolvanen@google.com,
masahiroy@kernel.org, maskray@google.com,
linux-kernel@vger.kernel.org, guoren@kernel.org,
roman.artemev@syntacore.com
Subject: Re: [PATCH] riscv: hwprobe: do not produce frtace relocation
Date: Tue, 26 Mar 2024 21:10:29 +0000 [thread overview]
Message-ID: <171148742940.11448.3731153346859499014.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240313085843.17661-1-vladimir.isaev@syntacore.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 13 Mar 2024 10:35:46 +0300 you wrote:
> Such relocation causes crash of android linker similar to one
> described in commit e05d57dcb8c7
> ("riscv: Fixup __vdso_gettimeofday broke dynamic ftrace").
>
> Looks like this relocation is added by CONFIG_DYNAMIC_FTRACE which is
> disabled in the default android kernel.
>
> [...]
Here is the summary with links:
- riscv: hwprobe: do not produce frtace relocation
https://git.kernel.org/riscv/c/ad14f7ca9f0d
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:[~2024-03-26 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 7:35 [PATCH] riscv: hwprobe: do not produce frtace relocation Vladimir Isaev
2024-03-19 3:54 ` Guo Ren
2024-03-26 8:56 ` Alexandre Ghiti
2024-03-26 21: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=171148742940.11448.3731153346859499014.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=catalin.marinas@arm.com \
--cc=evan@rivosinc.com \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=nicolas@fjasle.eu \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=roman.artemev@syntacore.com \
--cc=samitolvanen@google.com \
--cc=tglx@linutronix.de \
--cc=vladimir.isaev@syntacore.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