From: "Huang, Kai" <kai.huang@intel.com>
To: "jarkko@kernel.org" <jarkko@kernel.org>,
"x86@kernel.org" <x86@kernel.org>, "bp@alien8.de" <bp@alien8.de>,
"thorsten.blum@linux.dev" <thorsten.blum@linux.dev>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>
Cc: "linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/sgx: Fix typos and formatting in function comments
Date: Mon, 3 Nov 2025 23:47:11 +0000 [thread overview]
Message-ID: <717cb54f7ac6dd1f94a5c57c10a8cb377eb199bd.camel@intel.com> (raw)
In-Reply-To: <20251103090103.1415-2-thorsten.blum@linux.dev>
On Mon, 2025-11-03 at 10:01 +0100, Thorsten Blum wrote:
> Fix typos and formatting in function comments to clarify that
> sgx_set_attribute() returns 0, not -0, to avoid confusion and to be
> consistent.
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> arch/x86/kernel/cpu/sgx/main.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/sgx/main.c b/arch/x86/kernel/cpu/sgx/main.c
> index 2de01b379aa3..c33e2b56a3fc 100644
> --- a/arch/x86/kernel/cpu/sgx/main.c
> +++ b/arch/x86/kernel/cpu/sgx/main.c
> @@ -465,11 +465,11 @@ static struct sgx_epc_page *__sgx_alloc_epc_page_from_node(int nid)
> /**
> * __sgx_alloc_epc_page() - Allocate an EPC page
> *
> - * Iterate through NUMA nodes and reserve ia free EPC page to the caller. Start
> + * Iterate through NUMA nodes and reserve a free EPC page to the caller. Start
> * from the NUMA node, where the caller is executing.
> *
> * Return:
> - * - an EPC page: A borrowed EPC pages were available.
> + * - an EPC page: A borrowed EPC page if available.
> * - NULL: Out of EPC pages.
> */
Ack for fixing the typos.
> struct sgx_epc_page *__sgx_alloc_epc_page(void)
> @@ -898,8 +898,8 @@ static struct miscdevice sgx_dev_provision = {
> * /dev/sgx_provision is supported.
> *
> * Return:
> - * -0: SGX_ATTR_PROVISIONKEY is appended to allowed_attributes
> - * -EINVAL: Invalid, or not supported file descriptor
> + * - 0: SGX_ATTR_PROVISIONKEY is appended to allowed_attributes
> + * - -EINVAL: Invalid, or not supported file descriptor
> */
> int sgx_set_attribute(unsigned long *allowed_attributes,
> unsigned int attribute_fd)
It seems we don't have a consistent way of describing return values in the
k-doc comments in sgx/main.c. E.g.,
/**
* sgx_unmark_page_reclaimable() - Remove a page from the reclaim list
...
* Return:
* 0 on success,
* -EBUSY if the page is in the process of being reclaimed
*/
/**
* sgx_alloc_epc_page() - Allocate an EPC page
...
* Return:
* an EPC page,
* -errno on error
*/
Perhaps we should make them consistent in format.
But I think this can be done separately from fixing the typos. Maybe you
can split out the typo fixing as a separate patch, and have another patch to
fixing the return value description?
next prev parent reply other threads:[~2025-11-03 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 9:01 Thorsten Blum
2025-11-03 23:47 ` Huang, Kai [this message]
2025-11-04 19:13 ` Thorsten Blum
2025-11-04 21:01 ` Huang, Kai
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=717cb54f7ac6dd1f94a5c57c10a8cb377eb199bd.camel@intel.com \
--to=kai.huang@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@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=tglx@linutronix.de \
--cc=thorsten.blum@linux.dev \
--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
all inboxes | Powered by JetHome®