From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?UmFkaW0gS3LEjW3DocWZIDxya3JjbWFyQHZlbnRhbmFtaWNyby5jb20+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, debug@rivosinc.com
Subject: Re: [PATCH v2 0/4] riscv: minor thread_info.cpu improvements
Date: Wed, 06 Aug 2025 17:15:41 +0000 [thread overview]
Message-ID: <175450054199.2863135.9619865736779982038.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250725165410.2896641-3-rkrcmar@ventanamicro.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@rivosinc.com>:
On Fri, 25 Jul 2025 18:54:08 +0200 you wrote:
> Hello,
>
> I noticed that we give thread_info.cpu two different names in the
> assembly, load it as a wider type, and store it suboptimally.
>
> v2 is split for easy backporting.
>
> [...]
Here is the summary with links:
- [v2,1/4] riscv: use lw when reading int cpu in new_vmalloc_check
https://git.kernel.org/riscv/c/5fcea028d8b8
- [v2,2/4] riscv: use lw when reading int cpu in asm_per_cpu
https://git.kernel.org/riscv/c/47e006cf9789
- [v2,3/4] riscv: use TASK_TI_CPU instead of TASK_TI_CPU_NUM
https://git.kernel.org/riscv/c/a1984b2541b0
- [v2,4/4] riscv: pack rv64 thread_info better
https://git.kernel.org/riscv/c/9b3a86b7b14c
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:[~2025-08-06 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 16:54 [PATCH v2 0/4] riscv: minor thread_info.cpu improvements Radim Krčmář
2025-07-25 16:54 ` [PATCH v2 1/4] riscv: use lw when reading int cpu in new_vmalloc_check Radim Krčmář
2025-07-25 16:54 ` [PATCH v2 2/4] riscv: use lw when reading int cpu in asm_per_cpu Radim Krčmář
2025-07-25 16:54 ` [PATCH v2 3/4] riscv: use TASK_TI_CPU instead of TASK_TI_CPU_NUM Radim Krčmář
2025-07-25 16:54 ` [PATCH v2 4/4] riscv: pack rv64 thread_info better Radim Krčmář
2025-07-31 13:22 ` [PATCH v2 0/4] riscv: minor thread_info.cpu improvements Alexandre Ghiti
2025-08-06 17:15 ` 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=175450054199.2863135.9619865736779982038.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc==?utf-8?b?UmFkaW0gS3LEjW3DocWZIDxya3JjbWFyQHZlbnRhbmFtaWNyby5jb20+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=debug@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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