mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Zhu Wang <wangzhu9@huawei.com>
Cc: <mporter@kernel.crashing.org>, <alex.bou9@gmail.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] rapidio: fix -Wunused-const-variable= warning
Date: Wed, 26 Jul 2023 12:36:42 -0700	[thread overview]
Message-ID: <20230726123642.ab3f2c8382dfdb4fb62ae3e5@linux-foundation.org> (raw)
In-Reply-To: <20230726101714.169784-1-wangzhu9@huawei.com>

On Wed, 26 Jul 2023 18:17:14 +0800 Zhu Wang <wangzhu9@huawei.com> wrote:

> When building with W=1, the following warning occurs.
> 
> drivers/rapidio/rio_cm.c: In function ‘rio_txcq_handler’:
> drivers/rapidio/rio_cm.c:673:7: warning: variable ‘rc’ set but not used [-Wunused-but-set-variable]
>    int rc;
> 
> Since the variable "rc" is not used in function 'rio_txcq_handler',
> so we removed it to remove the warning.
> 
> ...
>
> --- a/drivers/rapidio/rio_cm.c
> +++ b/drivers/rapidio/rio_cm.c
> @@ -670,13 +670,12 @@ static void rio_txcq_handler(struct cm_dev *cm, int slot)
>  	 */
>  	if (!list_empty(&cm->tx_reqs) && (cm->tx_cnt < RIOCM_TX_RING_SIZE)) {
>  		struct tx_req *req, *_req;
> -		int rc;
>  
>  		list_for_each_entry_safe(req, _req, &cm->tx_reqs, node) {
>  			list_del(&req->node);
>  			cm->tx_buf[cm->tx_slot] = req->buffer;
> -			rc = rio_add_outb_message(cm->mport, req->rdev, cmbox,
> -						  req->buffer, req->len);
> +			rio_add_outb_message(cm->mport, req->rdev, cmbox,
> +					     req->buffer, req->len);
>  			kfree(req->buffer);
>  			kfree(req);

rio_add_outb_message() can fail.  It would be better to appropriately
handle these failures, rather than simply ignoring them.


      reply	other threads:[~2023-07-26 19:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 10:17 Zhu Wang
2023-07-26 19:36 ` Andrew Morton [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=20230726123642.ab3f2c8382dfdb4fb62ae3e5@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alex.bou9@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mporter@kernel.crashing.org \
    --cc=wangzhu9@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®