mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, vladimir.isaev@syntacore.com,
	roman.artemev@syntacore.com, guoren@kernel.org,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Prevent dynamic relocations in vDSO
Date: Thu, 17 Oct 2024 16:30:33 +0000	[thread overview]
Message-ID: <172918263324.2528145.12860614136206368233.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241016083625.136311-1-alexghiti@rivosinc.com>

Hello:

This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed, 16 Oct 2024 10:36:23 +0200 you wrote:
> Patch 2 uses a generic function to make sure the vDSO object does not
> contain any dynamic relocations.
> 
> Patch 1 removes a dynamic relocation from vDSO in rv32 found with patch
> 2.
> 
> v2: https://lore.kernel.org/linux-riscv/20240705060902.113294-1-alexghiti@rivosinc.com/
> v1: https://lore.kernel.org/linux-riscv/20240326113831.283025-1-alexghiti@rivosinc.com/
> 
> [...]

Here is the summary with links:
  - [v3,1/2] riscv: vdso: Prevent the compiler from inserting calls to memset()
    https://git.kernel.org/riscv/c/f431f67ff6c2
  - [v3,2/2] riscv: Check that vdso does not contain any dynamic relocations
    https://git.kernel.org/riscv/c/fcb5dcb789a2

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-10-17 16:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16  8:36 Alexandre Ghiti
2024-10-16  8:36 ` [PATCH v3 1/2] riscv: vdso: Prevent the compiler from inserting calls to memset() Alexandre Ghiti
2024-10-17  5:50   ` Guo Ren
2024-10-16  8:36 ` [PATCH v3 2/2] riscv: Check that vdso does not contain any dynamic relocations Alexandre Ghiti
2024-10-17  5:54   ` Guo Ren
2024-10-17 16:30 ` 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=172918263324.2528145.12860614136206368233.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alexghiti@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=guoren@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=roman.artemev@syntacore.com \
    --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
all inboxes | Powered by JetHome®