From: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Thara Gopinath <thara.gopinath@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Thara Gopinath <thara.gopinath@linaro.org>,
linux-crypto@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix Qualcomm Crypto engine self tests failures
Date: Wed, 17 Jun 2026 15:15:51 +0530 [thread overview]
Message-ID: <ce7ddb59-d219-4684-a56f-35ce4c3c345b@oss.qualcomm.com> (raw)
In-Reply-To: <4fzeulsheu5tam6pcymjqkqnqi3ibjgwchiefy27wr7b5i2yhk@4m47fpfbsmwf>
>> Seems Bartosz will be sending patches for algorithm removal changes.
>> The rest relevant selftests issues we'll fix accordingly.
>
> So, the old kernels will remain broken? Or do we expect to backport the
> cipher removal patches too?
Kindly see Barotsz series on top of this one[1].
Fixes will be backported on older kernels too.
[1]
https://lore.kernel.org/linux-arm-msm/20260615-qce-fix-self-tests-v2-0-dc911f1aad42@oss.qualcomm.com/
--
Regards
Kuldeep
prev parent reply other threads:[~2026-06-17 9:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 5:54 Kuldeep Singh
2026-06-10 5:54 ` [PATCH 1/2] crypto: qce: Fix xts-aes-qce for weak keys Kuldeep Singh
2026-06-12 0:40 ` Dmitry Baryshkov
2026-06-12 3:45 ` Herbert Xu
2026-06-12 6:11 ` Dmitry Baryshkov
2026-06-10 5:54 ` [PATCH 2/2] crypto: qce: Fix CTR-AES for partial block requests Kuldeep Singh
2026-06-10 18:46 ` Eric Biggers
2026-06-11 9:49 ` Kuldeep Singh
2026-06-10 18:42 ` [PATCH 0/2] Fix Qualcomm Crypto engine self tests failures Eric Biggers
2026-06-11 9:47 ` Kuldeep Singh
2026-06-12 0:43 ` Dmitry Baryshkov
2026-06-17 9:45 ` Kuldeep Singh [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=ce7ddb59-d219-4684-a56f-35ce4c3c345b@oss.qualcomm.com \
--to=kuldeep.singh@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=davem@davemloft.net \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thara.gopinath@gmail.com \
--cc=thara.gopinath@linaro.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 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®