From: larryw3i <larryw3i@yeah.net>
To: AlanSong-oc <AlanSong-oc@zhaoxin.com>,
Eric Biggers <ebiggers@kernel.org>,
linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
CobeChen@zhaoxin.com, GeorgeXue@zhaoxin.com, HansHu@zhaoxin.com,
LeoLiu-oc@zhaoxin.com, TonyWWang-oc@zhaoxin.com,
YunShen@zhaoxin.com
Subject: Re: [PATCH] crypto: padlock-sha - Disable broken driver
Date: Mon, 17 Nov 2025 18:08:07 +0800 [thread overview]
Message-ID: <c829e264-1cd0-4307-ac62-b75515ad3027@yeah.net> (raw)
In-Reply-To: <c24d0582-ae94-4dfb-ae6f-6baafa7fe689@zhaoxin.com>
On 11/17/25 17:03, AlanSong-oc wrote:
> I will submit the finalized patch immediately.
Dear AlanSong-oc,
I also want to nag a few more words. I think after a period of time,
most of your machines without external graphics cards may not be able to
install Debian properly (I don't know if KX-7000 is the same). It seems
that GNOME 49 no longer uses X11 by default but Wayland. However, as far
as I know, Wayland requires a graphics card driver to work. I have over
ten laptops with your CPUs built-in here. The operating system I
installed is Debian testing, but now GNOME is not working and I have to
use XFCE4. 😭
Regards,
larryw3i
next prev parent reply other threads:[~2025-11-17 10:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a1ed50c2-7338-4c97-8c36-84d2fa83d018@yeah.net>
2025-11-16 15:50 ` linux-image-amd64: self-tests for sha256 using sha256-padlock-nano failed larryw3i
2025-11-16 18:39 ` [PATCH] crypto: padlock-sha - Disable broken driver Eric Biggers
2025-11-17 9:03 ` AlanSong-oc
2025-11-17 10:08 ` larryw3i [this message]
2025-11-18 8:22 ` AlanSong-oc
2025-11-19 3:41 ` larryw3i
2025-11-18 3:34 ` Herbert Xu
2025-11-18 4:02 ` Eric Biggers
2025-12-17 4:30 ` AlanSong-oc
2025-12-17 4:56 ` Herbert Xu
2025-12-17 9:04 ` AlanSong-oc
2026-01-06 14:47 ` larryw3i
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=c829e264-1cd0-4307-ac62-b75515ad3027@yeah.net \
--to=larryw3i@yeah.net \
--cc=AlanSong-oc@zhaoxin.com \
--cc=CobeChen@zhaoxin.com \
--cc=GeorgeXue@zhaoxin.com \
--cc=HansHu@zhaoxin.com \
--cc=LeoLiu-oc@zhaoxin.com \
--cc=TonyWWang-oc@zhaoxin.com \
--cc=YunShen@zhaoxin.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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.