From: "Huang, Kai" <kai.huang@intel.com>
To: "seanjc@google.com" <seanjc@google.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"wangyuli@uniontech.com" <wangyuli@uniontech.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"xiangzelong@uniontech.com" <xiangzelong@uniontech.com>
Cc: "linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"jarkko@kernel.org" <jarkko@kernel.org>,
"x86@kernel.org" <x86@kernel.org>, "bp@suse.de" <bp@suse.de>,
"guanwentao@uniontech.com" <guanwentao@uniontech.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"sean.j.christopherson@intel.com"
<sean.j.christopherson@intel.com>,
"haitao.huang@linux.intel.com" <haitao.huang@linux.intel.com>,
"wubo@uniontech.com" <wubo@uniontech.com>
Subject: Re: [PATCH v3] x86/cpu: Adjust the error message when BIOS does not support SGX
Date: Sun, 25 Aug 2024 08:49:22 +0000 [thread overview]
Message-ID: <8cc1f0a0a4cb03007d52c040c05bf77f2fa16d6d.camel@intel.com> (raw)
In-Reply-To: <2FA59E9E3461354C+20240825081741.3890887-1-wangyuli@uniontech.com>
On Sun, 2024-08-25 at 16:17 +0800, WangYuli wrote:
> When SGX is not supported by the BIOS, the kernel log still output
> the error 'SGX disabled by BIOS', which can be confusing since
> there might not be an SGX-related option in the BIOS settings.
>
> As a kernel, it's difficult to distinguish between the BIOS not
> supporting SGX and the BIOS supporting SGX but it's disabled.
>
> Therefore, update the error message to
> 'SGX disabled or unsupported by BIOS' to make it easier for those
> reading kernel logs to understand what's happening.
>
> Reported-by: Bo Wu <wubo@uniontech.com>
> Closes: https://github.com/linuxdeepin/developer-center/issues/10032
> Acked-by: Kai Huang <kai.huang@intel.com>
> Link: https://lore.kernel.org/all/a30f7700c7817b3e7e2f2bdb37d5c10a318b2c3b.camel@intel.com/
> Signed-off-by: Zelong Xiang <xiangzelong@uniontech.com>
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
Hi Yuli,
When Thomas pointed out the "Signed-off-by chain is invalid" in v2:
https://lore.kernel.org/all/87zfpx4a0q.ffs@tglx/T/#mdc19b00c10177f3add9deaf505211bf8b3ec7110
I think it meant you either need to have a Co-developed-by for Zelong Xiang,
or you should remove his/her SoB. The reason is the patch is from you, but
not Zelong.
The SoB chain needs to reflect the chronological history of this patch. E.g.,
the SoB chain:
From: You
Co-developed-by: Zelong
Signed-off-by: Zelong
Signed-off-by: You
.. means the patch was originally generated by you, but Zelong also
participated in developing this patch before you finally signed off it.
For this one line code change patch, it doesn't make a lot sense to have
multiple developers, so I think you can just remove Zelong's SoB.
next prev parent reply other threads:[~2024-08-25 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 8:17 WangYuli
2024-08-25 8:49 ` Huang, Kai [this message]
2024-08-25 10:37 ` WangYuli
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=8cc1f0a0a4cb03007d52c040c05bf77f2fa16d6d.camel@intel.com \
--to=kai.huang@intel.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=guanwentao@uniontech.com \
--cc=haitao.huang@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=wangyuli@uniontech.com \
--cc=wubo@uniontech.com \
--cc=x86@kernel.org \
--cc=xiangzelong@uniontech.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
all inboxes | Powered by JetHome®