linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
	Dave Hansen <dave.hansen@linux.intel.com>,
	linux-sgx@vger.kernel.org
Subject: Re: [PATCH] x86/SGX: drop spurious kernel-doc notation
Date: Tue, 29 Jun 2021 23:22:53 +0300	[thread overview]
Message-ID: <20210629202253.qwqpaqoauz4usgle@kernel.org> (raw)
In-Reply-To: <20210627223639.27714-1-rdunlap@infradead.org>

On Sun, Jun 27, 2021 at 03:36:39PM -0700, Randy Dunlap wrote:
> Drop mistaken kernel-doc notation where plain C comments
> should be used instead.
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jarkko Sakkinen <jarkko@kernel.org>
> Cc: Dave Hansen <dave.hansen@linux.intel.com>
> Cc: linux-sgx@vger.kernel.org

"x86/SGX" -> "x86/sgx"

Anyway,

Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@kernel.org>

> ---
>  arch/x86/kernel/cpu/sgx/encl.h  |    2 +-
>  arch/x86/kernel/cpu/sgx/encls.h |    2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> --- linux-next-20210625.orig/arch/x86/kernel/cpu/sgx/encl.h
> +++ linux-next-20210625/arch/x86/kernel/cpu/sgx/encl.h
> @@ -1,5 +1,5 @@
>  /* SPDX-License-Identifier: GPL-2.0 */
> -/**
> +/*
>   * Copyright(c) 2016-20 Intel Corporation.
>   *
>   * Contains the software defined data structures for enclaves.
> --- linux-next-20210625.orig/arch/x86/kernel/cpu/sgx/encls.h
> +++ linux-next-20210625/arch/x86/kernel/cpu/sgx/encls.h
> @@ -11,7 +11,7 @@
>  #include <asm/traps.h>
>  #include "sgx.h"
>  
> -/**
> +/*
>   * ENCLS_FAULT_FLAG - flag signifying an ENCLS return code is a trapnr
>   *
>   * ENCLS has its own (positive value) error codes and also generates
> 

/Jarkko

      reply	other threads:[~2021-06-29 20:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27 22:36 Randy Dunlap
2021-06-29 20:22 ` Jarkko Sakkinen [this message]

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=20210629202253.qwqpaqoauz4usgle@kernel.org \
    --to=jarkko@kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sgx@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --subject='Re: [PATCH] x86/SGX: drop spurious kernel-doc notation' \
    /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

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).