From: "Alessandrelli, Daniele" <daniele.alessandrelli@intel.com>
To: "lee.jones@linaro.org" <lee.jones@linaro.org>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"Murphy, Declan" <declan.murphy@intel.com>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH 05/10] crypto: keembay: ocs-hcu: Fix incorrectly named functions/structs
Date: Thu, 18 Mar 2021 16:06:23 +0000 [thread overview]
Message-ID: <8fca1b8440cdf9b93effb88649f0512d2d154ef1.camel@intel.com> (raw)
In-Reply-To: <20210318124422.3200180-6-lee.jones@linaro.org>
On Thu, 2021-03-18 at 12:44 +0000, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/crypto/keembay/ocs-hcu.c:107: warning: expecting prototype for struct ocs_hcu_dma_list. Prototype was for struct ocs_hcu_dma_entry instead
> drivers/crypto/keembay/ocs-hcu.c:127: warning: expecting prototype for struct ocs_dma_list. Prototype was for struct ocs_hcu_dma_list instead
> drivers/crypto/keembay/ocs-hcu.c:610: warning: expecting prototype for ocs_hcu_digest(). Prototype was for ocs_hcu_hash_update() instead
> drivers/crypto/keembay/ocs-hcu.c:648: warning: expecting prototype for ocs_hcu_hash_final(). Prototype was for ocs_hcu_hash_finup() instead
>
> Cc: Daniele Alessandrelli <daniele.alessandrelli@intel.com>
> Cc: Declan Murphy <declan.murphy@intel.com>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: linux-crypto@vger.kernel.org
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
> ---
Reviewed-by: Daniele Alessandrelli <daniele.alessandrelli@intel.com>
Thanks for the fix!
> drivers/crypto/keembay/ocs-hcu.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/crypto/keembay/ocs-hcu.c b/drivers/crypto/keembay/ocs-hcu.c
> index 81eecacf603ad..deb9bd460ee62 100644
> --- a/drivers/crypto/keembay/ocs-hcu.c
> +++ b/drivers/crypto/keembay/ocs-hcu.c
> @@ -93,7 +93,7 @@
> #define OCS_HCU_WAIT_BUSY_TIMEOUT_US 1000000
>
> /**
> - * struct ocs_hcu_dma_list - An entry in an OCS DMA linked list.
> + * struct ocs_hcu_dma_entry - An entry in an OCS DMA linked list.
> * @src_addr: Source address of the data.
> * @src_len: Length of data to be fetched.
> * @nxt_desc: Next descriptor to fetch.
> @@ -107,7 +107,7 @@ struct ocs_hcu_dma_entry {
> };
>
> /**
> - * struct ocs_dma_list - OCS-specific DMA linked list.
> + * struct ocs_hcu_dma_list - OCS-specific DMA linked list.
> * @head: The head of the list (points to the array backing the list).
> * @tail: The current tail of the list; NULL if the list is empty.
> * @dma_addr: The DMA address of @head (i.e., the DMA address of the backing
> @@ -597,7 +597,7 @@ int ocs_hcu_hash_init(struct ocs_hcu_hash_ctx *ctx, enum ocs_hcu_algo algo)
> }
>
> /**
> - * ocs_hcu_digest() - Perform a hashing iteration.
> + * ocs_hcu_hash_update() - Perform a hashing iteration.
> * @hcu_dev: The OCS HCU device to use.
> * @ctx: The OCS HCU hashing context.
> * @dma_list: The OCS DMA list mapping the input data to process.
> @@ -632,7 +632,7 @@ int ocs_hcu_hash_update(struct ocs_hcu_dev *hcu_dev,
> }
>
> /**
> - * ocs_hcu_hash_final() - Update and finalize hash computation.
> + * ocs_hcu_hash_finup() - Update and finalize hash computation.
> * @hcu_dev: The OCS HCU device to use.
> * @ctx: The OCS HCU hashing context.
> * @dma_list: The OCS DMA list mapping the input data to process.
next prev parent reply other threads:[~2021-03-18 16:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 12:44 [PATCH v3 00/10] Rid W=1 warnings in Crypto Lee Jones
2021-03-18 12:44 ` [PATCH 01/10] crypto: hisilicon: sec_drv: Supply missing description for 'sec_queue_empty()'s 'queue' param Lee Jones
2021-03-18 12:44 ` [PATCH 02/10] crypto: bcm: Fix a whole host of kernel-doc misdemeanours Lee Jones
2021-03-18 12:44 ` [PATCH 03/10] crypto: chelsio: chcr_core: Fix some kernel-doc issues Lee Jones
2021-03-18 12:44 ` [PATCH 04/10] crypto: ux500: hash: hash_core: Fix worthy kernel-doc headers and remove others Lee Jones
2021-03-18 12:44 ` [PATCH 05/10] crypto: keembay: ocs-hcu: Fix incorrectly named functions/structs Lee Jones
2021-03-18 16:06 ` Alessandrelli, Daniele [this message]
2021-03-18 12:44 ` [PATCH 06/10] crypto: atmel-ecc: Struct headers need to start with keyword 'struct' Lee Jones
2021-03-22 9:12 ` Tudor.Ambarus
2021-03-18 12:44 ` [PATCH 07/10] crypto: caam: caampkc: Provide the name of the function and provide missing descriptions Lee Jones
2021-03-21 16:26 ` Horia Geantă
2021-03-18 12:44 ` [PATCH 08/10] crypto: vmx: Source headers are not good kernel-doc candidates Lee Jones
2021-03-18 12:44 ` [PATCH 09/10] crypto: nx: nx-aes-cbc: Repair some kernel-doc problems Lee Jones
2021-03-18 12:44 ` [PATCH 10/10] crypto: cavium: nitrox_isr: Demote non-compliant kernel-doc headers Lee Jones
2021-03-26 9:31 ` [PATCH v3 00/10] Rid W=1 warnings in Crypto Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2021-03-03 14:34 [PATCH v2 " Lee Jones
2021-03-03 14:34 ` [PATCH 05/10] crypto: keembay: ocs-hcu: Fix incorrectly named functions/structs Lee Jones
2021-03-04 12:02 ` Alessandrelli, Daniele
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=8fca1b8440cdf9b93effb88649f0512d2d154ef1.camel@intel.com \
--to=daniele.alessandrelli@intel.com \
--cc=davem@davemloft.net \
--cc=declan.murphy@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=lee.jones@linaro.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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®