linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marilene Andrade Garcia <marilene.agarcia@gmail.com>
To: Coly Li <colyli@suse.de>, Kent Overstreet <kent.overstreet@linux.dev>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	Javier Carrasco <javier.carrasco.cruz@gmail.com>,
	linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bcache: Fix compiler warnings
Date: Wed, 5 Jun 2024 19:27:36 -0300	[thread overview]
Message-ID: <cba4f849-8443-405b-8318-a7208e6b80cc@gmail.com> (raw)
In-Reply-To: <20240605034057.2671663-1-marilene.agarcia@gmail.com>

On 05/06/2024 00:40, Marilene A Garcia wrote:
> It fixes the following compiler warnings by
> using "/*" instead of "/**" in the comments
> 
> drivers/md/bcache/request.c:309: warning:
> Function parameter or struct member 'bch_data_insert'
> not described in 'CLOSURE_CALLBACK'
> 
> drivers/md/bcache/request.c:309: warning: expecting
> prototype for bch_data_insert(). Prototype was for
> CLOSURE_CALLBACK() instead
> 
> Signed-off-by: Marilene A Garcia <marilene.agarcia@gmail.com>
> ---
> Hello,
> These warnings happen using GCC compiler the command 'make W=1'.
> 
> Thank you.
> 
>   drivers/md/bcache/request.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/md/bcache/request.c b/drivers/md/bcache/request.c
> index af345dc6fde1..457b9605aff9 100644
> --- a/drivers/md/bcache/request.c
> +++ b/drivers/md/bcache/request.c
> @@ -285,7 +285,7 @@ static CLOSURE_CALLBACK(bch_data_insert_start)
>   	}
>   }
>   
> -/**
> +/*
>    * bch_data_insert - stick some data in the cache
>    * @cl: closure pointer.
>    *

Hello,
I have realized that even though this change could fix the warning, it 
is not the correct fix to it, because it breaks the format of kernel 
function comments.

So please discard the patch.
Thank you.

      reply	other threads:[~2024-06-05 22:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05  3:40 [PATCH] bcache: Fix compiler warnings Marilene A Garcia
2024-06-05 22:27 ` Marilene Andrade Garcia [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=cba4f849-8443-405b-8318-a7208e6b80cc@gmail.com \
    --to=marilene.agarcia@gmail.com \
    --cc=colyli@suse.de \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).