From: David Laight <david.laight.linux@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Alexander Usyskin <alexander.usyskin@intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vitaly Lubart <lubvital@gmail.com>,
Karol Wachowski <karol.wachowski@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] issei: INTEL_SSEI should depend on X86
Date: Wed, 26 Aug 2026 10:08:48 +0100 [thread overview]
Message-ID: <20260826100848.12eaf40e@pumpkin> (raw)
In-Reply-To: <7145ead76cf7cf399eb4e1e6039f51cae07b49b4.1786009079.git.geert+renesas@glider.be>
On Thu, 6 Aug 2026 11:46:55 +0200
Geert Uytterhoeven <geert+renesas@glider.be> wrote:
> The Intel Silicon Security Engine is only present on systems with Intel
> Lunar Lake CPUs. Hence add a dependency on X86, to prevent asking the
> user about this subsystem when configuring a kernel for a non-x86
> architecture.
Should it be X86_64 ?
>
> Fixes: 65f0ecb9ec85cb3a ("issei: initial driver skeleton")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/misc/issei/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/misc/issei/Kconfig b/drivers/misc/issei/Kconfig
> index 12a3fd80996946c2..bd452c95aa6de46b 100644
> --- a/drivers/misc/issei/Kconfig
> +++ b/drivers/misc/issei/Kconfig
> @@ -2,6 +2,7 @@
> # Copyright (C) 2023-2026 Intel Corporation
> config INTEL_SSEI
> tristate "Intel Silicon Security Engine Interface"
> + depends on X86 || COMPILE_TEST
> help
> The ISSEI (Intel Silicon Security Engine Interface)
> subsystem provides a communication channel between the host and the
prev parent reply other threads:[~2026-08-26 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 9:46 [PATCH] issei: INTEL_SSEI should depend on X86 Geert Uytterhoeven
2026-08-26 6:50 ` Usyskin, Alexander
2026-08-26 9:08 ` David Laight [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=20260826100848.12eaf40e@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=alexander.usyskin@intel.com \
--cc=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=karol.wachowski@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lubvital@gmail.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