From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/cxgbe: remove useless address check
Date: Tue, 5 Oct 2021 01:02:06 +0530 [thread overview]
Message-ID: <20211004193205.GA17631@chelsio.com> (raw)
In-Reply-To: <20211004172754.3461732-1-ferruh.yigit@intel.com>
On Monday, October 10/04/21, 2021 at 18:27:54 +0100, Ferruh Yigit wrote:
> reported by "gcc (GCC) 12.0.0 20211003 (experimental)":
>
> ../drivers/net/cxgbe/cxgbe_ethdev.c:
> In function ‘cxgbe_dev_rx_queue_setup’:
> ../drivers/net/cxgbe/cxgbe_ethdev.c:682:24:
> error: the comparison will always evaluate as ‘true’ for the
> address of ‘fl’ will never be NULL [-Werror=address]
> 682 | if ((&rxq->fl) != NULL)
> | ^~
>
> Fixing it by removing useless check.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Looks good. Thanks for fixing it up.
Reviewed-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
next prev parent reply other threads:[~2021-10-04 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 17:27 Ferruh Yigit
2021-10-04 19:32 ` Rahul Lakkireddy [this message]
2021-10-06 11:33 ` Ferruh Yigit
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=20211004193205.GA17631@chelsio.com \
--to=rahul.lakkireddy@chelsio.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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;
as well as URLs for NNTP newsgroup(s).