From: patchwork-bot+linux-riscv@kernel.org
To: Andy Chiu <tchiu@tenstorrent.com>
Cc: linux-riscv@lists.infradead.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
andybnac@gmail.com, dfustini@oss.tenstorrent.com,
greentime.hu@sifive.com, linux-kernel@vger.kernel.org,
olof@lixom.net
Subject: Re: [PATCH v1 0/2] riscv: runtime enablement for native misaligned ucopy
Date: Tue, 06 Oct 2026 09:40:10 +0000 [thread overview]
Message-ID: <179127961027.2107992.5336345145060413081.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260911182402.1434257-1-tchiu@tenstorrent.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:
On Fri, 11 Sep 2026 13:23:58 -0500 you wrote:
> This series is the continued series for commit b94cec5761d2 ("riscv:
> skip software algning code for HAVE_EFFICIENT_UNALIGNED_ACCESS") that
> makes the optimization available to distro kernels compiled without
> NONPORTABLE config. Now, the kernel can skip the software aligning code
> in ucopy after fast unaligned access is detected at runtime.
>
> Andy Chiu (2):
> riscv: introduce assembly version of jump table
> riscv: optmize ucopy for has_fast_unaligned_accesses
>
> [...]
Here is the summary with links:
- [v1,1/2] riscv: introduce assembly version of jump table
https://git.kernel.org/riscv/c/57ae2ff9fcec
- [v1,2/2] riscv: optmize ucopy for has_fast_unaligned_accesses
https://git.kernel.org/riscv/c/e76892c7ad3e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-10-06 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 18:23 Andy Chiu
2026-10-06 9:40 ` patchwork-bot+linux-riscv [this message]
2026-10-06 10:16 ` Paul Walmsley
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=179127961027.2107992.5336345145060413081.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=dfustini@oss.tenstorrent.com \
--cc=greentime.hu@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=olof@lixom.net \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=tchiu@tenstorrent.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®