Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1172486pxf; Fri, 26 Mar 2021 02:37:31 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwkJAC7k7QViql5xFWQV5kR0NX23BUSCQ/Hq4CH2cUXsVta17RZ+Vz2ezDQGTiSoSoIThQ4 X-Received: by 2002:a17:906:f210:: with SMTP id gt16mr14227267ejb.206.1616751451102; Fri, 26 Mar 2021 02:37:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616751451; cv=none; d=google.com; s=arc-20160816; b=ZFnmUOUxRtaVZFh16p+Msp1acCrI9LmwAJVp0IOWLZUE6WEu8+epnBhYxVs2KaxE8F JFXn+EQoJSHn75tXDp4wiseBE7HZmnvDxLWZ2xB6DLFPYmGirgZVmKWgkDGa6gDHRHK4 xuuPkZdLwSIh+G7TjPUHnTVxrvfUFTQDDmoRGJapkR3gh2qKcfRoEz6BlHyJLXMo77R/ 7w3q3FLjCkxw8n48VQuC5Nv2KOXaiQ+Ed/TtewQKvQo2d7kKeqEeHCQrI7fGemyj/qlv ITTYcjrD1SGRnpdoED6BbfmNdoTg/3S02Peec3t/4ookGrulp3ycD55ogCUqxnVxYFwp OeXg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=oEIWKuch5H9xznLZmzBR3RBIl6wGzBRIplVil1hLBuc=; b=DRXfTshOlMuWXX4MkcdmKUM1tm3EFw7q/I98iG0a9HRpBZnYMF39qa8fdQ9+Nd6DYX lTM7p3uawISMGbU77epPOoqRLq8DTfhfmxXueIlIjD1tafVMskDAas4KLrHT1s3bqqyU SCrunEiQJqEKudcmMOgEx4aJnCKvgyyexGbtHbTawSs5rDsAPgipL5YQLFkbGdyCSCTS IarSavufAW4Z5wP3O0oceahZK3Y/t5AfA0g0hPOHTRw7R0SWOJwXy9UcHUisum+tJyqz 3U8mcQww5WPAmRcKd3w0Hdf9KGii3YSd4S63cRxbaOnB/HyzJjSp+ifCkKWfwVQSKiyQ VEBQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id de11si6161934edb.15.2021.03.26.02.37.07; Fri, 26 Mar 2021 02:37:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230259AbhCZJfh (ORCPT + 99 others); Fri, 26 Mar 2021 05:35:37 -0400 Received: from helcar.hmeau.com ([216.24.177.18]:35630 "EHLO fornost.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230472AbhCZJfQ (ORCPT ); Fri, 26 Mar 2021 05:35:16 -0400 Received: from gwarestrin.arnor.me.apana.org.au ([192.168.103.7]) by fornost.hmeau.com with smtp (Exim 4.92 #5 (Debian)) id 1lPiro-0003ea-N5; Fri, 26 Mar 2021 20:34:57 +1100 Received: by gwarestrin.arnor.me.apana.org.au (sSMTP sendmail emulation); Fri, 26 Mar 2021 20:34:56 +1100 Date: Fri, 26 Mar 2021 20:34:56 +1100 From: Herbert Xu To: Aditya Srivastava Cc: linux-kernel@vger.kernel.org, lukas.bulwahn@gmail.com, corbet@lwn.net, rdunlap@infradead.org, linux-kernel-mentees@lists.linuxfoundation.org, leitao@debian.org, nayna@linux.ibm.com, pfsmorigo@gmail.com, mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org, davem@davemloft.net, linux-crypto@vger.kernel.org, linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH] crypto: nx: fix incorrect kernel-doc comment syntax in files Message-ID: <20210326093456.GS12658@gondor.apana.org.au> References: <20210321123007.15505-1-yashsri421@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210321123007.15505-1-yashsri421@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Sun, Mar 21, 2021 at 06:00:07PM +0530, Aditya Srivastava wrote: > The opening comment mark '/**' is used for highlighting the beginning of > kernel-doc comments. > There are certain files in drivers/crypto/nx, which follow this syntax, > but the content inside does not comply with kernel-doc. > Such lines were probably not meant for kernel-doc parsing, but are parsed > due to the presence of kernel-doc like comment syntax(i.e, '/**'), which > causes unexpected warnings from kernel-doc. > > E.g., presence of kernel-doc like comment in the header lines for > drivers/crypto/nx/nx-sha256.c at header causes these warnings: > "warning: Function parameter or member 'tfm' not described in 'nx_crypto_ctx_sha256_init'" > "warning: expecting prototype for SHA(). Prototype was for nx_crypto_ctx_sha256_init() instead" > > Similarly for other files too. > > Provide a simple fix by replacing such occurrences with general comment > format, i.e. '/*', to prevent kernel-doc from parsing it. > > Signed-off-by: Aditya Srivastava > --- > * Applies perfectly on next-20210319 > > drivers/crypto/nx/nx-aes-cbc.c | 2 +- > drivers/crypto/nx/nx-aes-ccm.c | 2 +- > drivers/crypto/nx/nx-aes-ctr.c | 2 +- > drivers/crypto/nx/nx-aes-ecb.c | 2 +- > drivers/crypto/nx/nx-aes-gcm.c | 2 +- > drivers/crypto/nx/nx-aes-xcbc.c | 2 +- > drivers/crypto/nx/nx-sha256.c | 2 +- > drivers/crypto/nx/nx-sha512.c | 2 +- > drivers/crypto/nx/nx.c | 2 +- > drivers/crypto/nx/nx_debugfs.c | 2 +- > 10 files changed, 10 insertions(+), 10 deletions(-) Patch applied. Thanks. -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt