[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0d7697fd-11b3-1d4a-78da-7e5eb293d186@quicinc.com>
Date: Sun, 27 Aug 2023 14:26:33 -0700
From: Trilok Soni <quic_tsoni@...cinc.com>
To: Maximilian Luz <luzmaximilian@...il.com>,
Bjorn Andersson <andersson@...nel.org>
CC: Andy Gross <agross@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Ard Biesheuvel <ardb@...nel.org>,
Ilias Apalodimas <ilias.apalodimas@...aro.org>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Sudeep Holla <sudeep.holla@....com>,
Johan Hovold <johan@...nel.org>,
Steev Klimaszewski <steev@...i.org>,
<linux-arm-msm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Johan Hovold <johan+linaro@...nel.org>
Subject: Re: [PATCH v6 3/3] firmware: Add support for Qualcomm UEFI Secure
Application
On 8/27/2023 2:14 PM, Maximilian Luz wrote:
>
> +config QCOM_QSEECOM_UEFISECAPP
> + bool "Qualcomm SEE UEFI Secure App client driver"
Why not "tristate"? This driver can be a loadable module, right?
> + depends on QCOM_QSEECOM
> + depends on EFI
> + help
--
---Trilok Soni
Powered by blists - more mailing lists