linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Huang, Kai" <kai.huang@intel.com>
To: "Reshetova, Elena" <elena.reshetova@intel.com>,
	"Hansen, Dave" <dave.hansen@intel.com>
Cc: "linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
	"mingo@kernel.org" <mingo@kernel.org>,
	"Scarlata, Vincent R" <vincent.r.scarlata@intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"jarkko@kernel.org" <jarkko@kernel.org>,
	"Annapurve, Vishal" <vannapurve@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Mallick, Asit K" <asit.k.mallick@intel.com>,
	"Aktas, Erdem" <erdemaktas@google.com>,
	"Cai, Chong" <chongc@google.com>,
	"Bondarevska, Nataliia" <bondarn@google.com>,
	"seanjc@google.com" <seanjc@google.com>,
	"Raynor, Scott" <scott.raynor@intel.com>
Subject: Re: [PATCH v14 4/5] x86/sgx: Implement ENCLS[EUPDATESVN]
Date: Thu, 14 Aug 2025 22:31:00 +0000	[thread overview]
Message-ID: <f5e9a2fc1b3f11ed8bf1525a53d0f7ce830200c5.camel@intel.com> (raw)
In-Reply-To: <DM8PR11MB5750E0E7EE14FA87E9C48336E735A@DM8PR11MB5750.namprd11.prod.outlook.com>


> > 
> > > 
> > > + * Return:
> > > + * * %0:		- Success or not supported
> > > + * * %-EAGAIN:		- Can be safely retried, failure is due to lack of
> > > + * *			entropy in RNG
> > 
> > Nit: if another version is ever needed, I think it would be better to make
> > the text vertical aligned w/o the leading '-', i.e.,
> > 
> > 	* %-EAGAIN:	- Can be ....
> > 			  entropy in RNG.
> > 
> > .. instead of
> > 
> > 	* %-EAGAIN:	- Can be ....
> > 			entropy in RNG.
> 
> OK, yes, this can be fixed, indeed. 
> 

I downloaded those patches and checked locally.  I found there's an
unnecessary 'tab' between the error codes and the descriptions, making the
whitespace between them unnecessarily too long.

Please see below diff I came up with:

diff --git a/arch/x86/kernel/cpu/sgx/main.c
b/arch/x86/kernel/cpu/sgx/main.c
index cff5c4d22ac2..c6467628da04 100644
--- a/arch/x86/kernel/cpu/sgx/main.c
+++ b/arch/x86/kernel/cpu/sgx/main.c
@@ -929,10 +929,10 @@ static int sgx_usage_count;
  * cryptographic assets.
  *
  * Return:
- * * %0:               - Success or not supported
- * * %-EAGAIN:         - Can be safely retried, failure is due to lack of
- * *                   entropy in RNG
- * * %-EIO:            - Unexpected error, retries are not advisable
+ * * %0:       - Success or not supported
+ * * %-EAGAIN: - Can be safely retried, failure is due to lack of
+ * *             entropy in RNG
+ * * %-EIO:    - Unexpected error, retries are not advisable
  */
 static int sgx_update_svn(void)
 {

  reply	other threads:[~2025-08-14 22:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14  7:34 [PATCH v14 0/5] Enable automatic SVN updates for SGX enclaves Elena Reshetova
2025-08-14  7:34 ` [PATCH v14 1/5] x86/sgx: Introduce functions to count the sgx_(vepc_)open() Elena Reshetova
2025-08-14  7:34 ` [PATCH v14 2/5] x86/cpufeatures: Add X86_FEATURE_SGX_EUPDATESVN feature flag Elena Reshetova
2025-08-14  7:34 ` [PATCH v14 3/5] x86/sgx: Define error codes for use by ENCLS[EUPDATESVN] Elena Reshetova
2025-08-14  7:34 ` [PATCH v14 4/5] x86/sgx: Implement ENCLS[EUPDATESVN] Elena Reshetova
2025-08-14  9:35   ` Huang, Kai
2025-08-14 11:48     ` Reshetova, Elena
2025-08-14 22:31       ` Huang, Kai [this message]
2025-08-15 12:05         ` Reshetova, Elena
2025-08-14  7:34 ` [PATCH v14 5/5] x86/sgx: Enable automatic SVN updates for SGX enclaves Elena Reshetova
2025-08-14  9:36   ` Huang, Kai
2025-08-14 16:50   ` Dave Hansen
2025-08-14 21:40     ` Huang, Kai
2025-08-15  6:59       ` Reshetova, Elena
2025-08-18  5:03         ` Huang, Kai
2025-08-18  5:41           ` Reshetova, Elena

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=f5e9a2fc1b3f11ed8bf1525a53d0f7ce830200c5.camel@intel.com \
    --to=kai.huang@intel.com \
    --cc=asit.k.mallick@intel.com \
    --cc=bondarn@google.com \
    --cc=chongc@google.com \
    --cc=dave.hansen@intel.com \
    --cc=elena.reshetova@intel.com \
    --cc=erdemaktas@google.com \
    --cc=jarkko@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sgx@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=scott.raynor@intel.com \
    --cc=seanjc@google.com \
    --cc=vannapurve@google.com \
    --cc=vincent.r.scarlata@intel.com \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).