[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <66f1f4e39de4314f9c1b7a6d7cd6914e42a20217.camel@intel.com>
Date: Tue, 02 Mar 2021 01:08:25 +1300
From: Kai Huang <kai.huang@...el.com>
To: Borislav Petkov <bp@...en8.de>
Cc: kvm@...r.kernel.org, x86@...nel.org, linux-sgx@...r.kernel.org,
linux-kernel@...r.kernel.org, seanjc@...gle.com, jarkko@...nel.org,
luto@...nel.org, dave.hansen@...el.com, rick.p.edgecombe@...el.com,
haitao.huang@...el.com, pbonzini@...hat.com, tglx@...utronix.de,
mingo@...hat.com, hpa@...or.com
Subject: Re: [PATCH 02/25] x86/cpufeatures: Add SGX1 and SGX2 sub-features
On Mon, 2021-03-01 at 12:58 +0100, Borislav Petkov wrote:
> On Tue, Mar 02, 2021 at 12:43:06AM +1300, Kai Huang wrote:
> > To confirm, if we suppress both "sgx1" and "sgx2" in /proc/cpuinfo, we
> > don't need to add "why to suppress" in commit message, right?
>
> You should always explain in a patch why you're doing the change. So
> that a reviewer knows. And then people in the future can follow why
> you've made that decision. Always.
Got it. Thanks.
Powered by blists - more mailing lists