From: patchwork-bot+linux-riscv@kernel.org
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, re@w6rz.net,
samuel.holland@sifive.com, schwab@linux-m68k.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] riscv: Fix issues with module loading
Date: Wed, 06 Dec 2023 12:10:23 +0000 [thread overview]
Message-ID: <170186462381.31416.3360582134576570262.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231127-module_linking_freeing-v4-0-a2ca1d7027d0@rivosinc.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 27 Nov 2023 14:04:58 -0800 you wrote:
> Module loading did not account for multiple threads concurrently loading
> modules. This patch fixes that issue. There is also a small patch to fix
> the type of a __le16 variable.
>
> Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
> ---
> Changes in v4:
> - Make functions only used internally static
> - Free data structures on kmalloc failure (Andreas)
> - Link to v3: https://lore.kernel.org/r/20231122-module_linking_freeing-v3-0-8e9e412a3305@rivosinc.com
>
> [...]
Here is the summary with links:
- [v4,1/2] riscv: Safely remove entries from relocation list
https://git.kernel.org/riscv/c/d8792a5734b0
- [v4,2/2] riscv: Correct type casting in module loading
https://git.kernel.org/riscv/c/4a92a87950c4
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-12-06 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 22:04 [PATCH v4 0/2] riscv: Fix issues with module loading Charlie Jenkins
2023-11-27 22:04 ` [PATCH v4 1/2] riscv: Safely remove entries from relocation list Charlie Jenkins
2023-11-29 7:29 ` Björn Töpel
2023-12-04 20:30 ` Lad, Prabhakar
2023-11-27 22:05 ` [PATCH v4 2/2] riscv: Correct type casting in module loading Charlie Jenkins
2023-12-04 20:32 ` Lad, Prabhakar
2023-11-29 7:26 ` [PATCH v4 0/2] riscv: Fix issues with " Björn Töpel
2023-12-06 12: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=170186462381.31416.3360582134576570262.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=re@w6rz.net \
--cc=samuel.holland@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