From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,hch@lst.de,akpm@linux-foundation.org
Subject: [folded-merged] raid6-rework-registration-of-optimized-algorithms-fix.patch removed from -mm tree
Date: Thu, 28 May 2026 21:18:47 -0700 [thread overview]
Message-ID: <20260529041847.CBFC71F00893@smtp.kernel.org> (raw)
The quilt patch titled
Subject: raid6/x86: register avx512 after avx2
has been removed from the -mm tree. Its filename was
raid6-rework-registration-of-optimized-algorithms-fix.patch
This patch was dropped because it was folded into raid6-rework-registration-of-optimized-algorithms.patch
------------------------------------------------------
From: Christoph Hellwig <hch@lst.de>
Subject: raid6/x86: register avx512 after avx2
Date: Wed, 27 May 2026 09:45:26 +0200
This way non-benchmarks configs still get avx512 if supported.
Link: https://lore.kernel.org/20260527074539.2292913-3-hch@lst.de
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/raid/raid6/x86/pq_arch.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--- a/lib/raid/raid6/x86/pq_arch.h~raid6-rework-registration-of-optimized-algorithms-fix
+++ a/lib/raid/raid6/x86/pq_arch.h
@@ -60,16 +60,16 @@ static inline bool raid6_has_sse1_or_mmx
static __always_inline void __init arch_raid6_init(void)
{
if (raid6_has_avx2()) {
+ raid6_algo_add(&raid6_avx2x1);
+ raid6_algo_add(&raid6_avx2x2);
+ if (IS_ENABLED(CONFIG_X86_64))
+ raid6_algo_add(&raid6_avx2x4);
if (raid6_has_avx512()) {
raid6_algo_add(&raid6_avx512x1);
raid6_algo_add(&raid6_avx512x2);
if (IS_ENABLED(CONFIG_X86_64))
raid6_algo_add(&raid6_avx512x4);
}
- raid6_algo_add(&raid6_avx2x1);
- raid6_algo_add(&raid6_avx2x2);
- if (IS_ENABLED(CONFIG_X86_64))
- raid6_algo_add(&raid6_avx2x4);
} else if (IS_ENABLED(CONFIG_X86_64) || raid6_has_sse2()) {
/* x86_64 can assume SSE2 as baseline */
raid6_algo_add(&raid6_sse2x1);
_
Patches currently in -mm which might be from hch@lst.de are
raid6-turn-the-userspace-test-harness-into-a-kunit-test.patch
raid6-remove-__kernel__-ifdefs.patch
raid6-move-to-lib-raid.patch
raid6-remove-unused-defines-in-pqh.patch
raid6-remove-raid6_get_zero_page.patch
raid6-use-named-initializers-for-struct-raid6_calls.patch
raid6-improve-the-public-interface.patch
raid6-warn-when-using-less-than-four-devices.patch
raid6-hide-internals.patch
raid6-rework-registration-of-optimized-algorithms.patch
raid6-use-static_call-for-gen_syndrom-and-xor_syndrom.patch
raid6-use-static_call-for-raid6_recov_2data-and-raid6_recov_datap.patch
raid6-update-top-of-file-comments.patch
raid6_kunit-use-kunit_case_param.patch
raid6_kunit-dynamically-allocate-data-buffers-using-vmalloc.patch
raid6_kunit-cleanup-dataptr-handling.patch
raid6_kunit-randomize-parameters-and-increase-limits.patch
raid6_kunit-randomize-buffer-alignment.patch
reply other threads:[~2026-05-29 4:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260529041847.CBFC71F00893@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=mm-commits@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.