mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: YueHaibing <yuehaibing@huawei.com>,
	colyli@suse.de, akpm@linux-foundation.org,
	grandmaster@al2klimov.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] lib: crc64: Fix kernel-doc warning
Date: Tue, 1 Jun 2021 11:24:10 -0700	[thread overview]
Message-ID: <68b5af53-d4c3-b5cd-8c2b-1d306d1fdb07@infradead.org> (raw)
In-Reply-To: <20210601135851.15444-1-yuehaibing@huawei.com>

On 6/1/21 6:58 AM, YueHaibing wrote:
> Fix W=1 kernel build warning:
> 
> lib/crc64.c:40: warning:
>  bad line:         or the previous crc64 value if computing incrementally.
> 
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>

Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>


Thanks.

> ---
>  lib/crc64.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/crc64.c b/lib/crc64.c
> index 47cfa054827f..9f852a89ee2a 100644
> --- a/lib/crc64.c
> +++ b/lib/crc64.c
> @@ -37,7 +37,7 @@ MODULE_LICENSE("GPL v2");
>  /**
>   * crc64_be - Calculate bitwise big-endian ECMA-182 CRC64
>   * @crc: seed value for computation. 0 or (u64)~0 for a new CRC calculation,
> -	or the previous crc64 value if computing incrementally.
> + *       or the previous crc64 value if computing incrementally.
>   * @p: pointer to buffer over which CRC64 is run
>   * @len: length of buffer @p
>   */
> 


-- 
~Randy

      parent reply	other threads:[~2021-06-01 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 13:58 YueHaibing
2021-06-01 14:03 ` Coly Li
2021-06-01 18:24 ` Randy Dunlap [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=68b5af53-d4c3-b5cd-8c2b-1d306d1fdb07@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=colyli@suse.de \
    --cc=grandmaster@al2klimov.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuehaibing@huawei.com \
    /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®