Re: [PATCH 09/25] xor: move generic implementations out of asm-generic/xor.h
Christoph Hellwig <[email protected]>
| Newsgroups | org.kernel.vger.sparclinux,dev.linux.lists.loongarch,org.infradead.lists.linux-riscv,org.infradead.lists.linux-um,org.kernel.vger.linux-alpha,org.kernel.vger.linux-arch,org.kernel.vger.linux-btrfs,org.kernel.vger.linux-crypto,org.kernel.vger.linux-kernel,org.kernel.vger.linux-raid,org.kernel.vger.linux-s390,org.ozlabs.lists.linuxppc-dev |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Mar 03, 2026 at 05:09:11PM +0100, Christoph Hellwig wrote: > And earlier version did this, but it's a bit ugly. What I might > consider is to require architectures that provide optimized version > to opt into any generic one they want to use. This would require > extra kconfig symbols, but be a lot cleaner overall. I looked into this, but because the static_call requires a default version I gave up on it for now. In theory we could build just a single generic one for that and make the others optional, but that feels a bit odd.