From: patchwork-bot+linux-riscv@kernel.org
To: Samuel Holland <samuel.holland@sifive.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] riscv: CPU operations cleanup
Date: Fri, 05 Jan 2024 21:50:27 +0000 [thread overview]
Message-ID: <170449142782.26226.4217701485670023420.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231121234736.3489608-1-samuel.holland@sifive.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 21 Nov 2023 15:47:23 -0800 you wrote:
> This series cleans up some duplicated and dead code around the RISC-V
> CPU operations, that was copied from arm64 but is not needed here. The
> result is a bit of memory savings and removal of a few SBI calls during
> boot, with no functional change.
>
>
> Samuel Holland (3):
> riscv: Deduplicate code in setup_smp()
> riscv: Remove unused members from struct cpu_operations
> riscv: Use the same CPU operations for all CPUs
>
> [...]
Here is the summary with links:
- [1/3] riscv: Deduplicate code in setup_smp()
https://git.kernel.org/riscv/c/a4166aec1130
- [2/3] riscv: Remove unused members from struct cpu_operations
https://git.kernel.org/riscv/c/79093f3ec39c
- [3/3] riscv: Use the same CPU operations for all CPUs
https://git.kernel.org/riscv/c/62ff262227a4
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-01-05 21:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 23:47 [PATCH 0/3] riscv: CPU operations cleanup Samuel Holland
2023-11-21 23:47 ` [PATCH 1/3] riscv: Deduplicate code in setup_smp() Samuel Holland
2023-11-22 11:18 ` Conor Dooley
2023-11-21 23:47 ` [PATCH 2/3] riscv: Remove unused members from struct cpu_operations Samuel Holland
2023-11-22 11:28 ` Conor Dooley
2023-11-21 23:47 ` [PATCH 3/3] riscv: Use the same CPU operations for all CPUs Samuel Holland
2023-11-22 11:39 ` Conor Dooley
2024-01-05 21:50 ` 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=170449142782.26226.4217701485670023420.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=samuel.holland@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