From: Bruce Richardson <bruce.richardson@intel.com>
To: Venkatesh Vemula <venkatesh.vemula@intel.com>
Cc: <dev@dpdk.org>,
<aman.deep.singh@bricha3-mobl1.ger.corp.intel.com>,
<shaiq.wani@intel.com>
Subject: Re: [PATCH v1] net/intel: changes to avoid comma operator misuse warnings
Date: Mon, 17 Nov 2025 11:54:51 +0000 [thread overview]
Message-ID: <aRsNC26UxgWgozZb@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20251106082354.1534181-1-venkatesh.vemula@intel.com>
On Thu, Nov 06, 2025 at 01:53:54PM +0530, Venkatesh Vemula wrote:
> fixed comma operator misuse warnings with clang compiler
> for intel PMDs when -Wcomma enabled.
>
> Bugzilla ID: 1809("net/intel: possible misuse of comma operator")
> Signed-off-by: Venkatesh Vemula <venkatesh.vemula@intel.com>
> ---
> drivers/net/intel/i40e/i40e_ethdev.c | 8 ++++----
> drivers/net/intel/i40e/i40e_rxtx_vec_avx2.c | 4 ++--
> drivers/net/intel/i40e/i40e_rxtx_vec_avx512.c | 2 +-
> drivers/net/intel/iavf/iavf_rxtx_vec_avx2.c | 4 ++--
> drivers/net/intel/iavf/iavf_rxtx_vec_avx512.c | 6 +++---
> drivers/net/intel/ice/ice_ethdev.c | 8 ++++----
> drivers/net/intel/ice/ice_rxtx_vec_avx2.c | 4 ++--
> drivers/net/intel/ice/ice_rxtx_vec_avx512.c | 2 +-
> drivers/net/intel/idpf/idpf_common_rxtx_avx2.c | 4 ++--
> drivers/net/intel/idpf/idpf_common_rxtx_avx512.c | 8 ++++----
> 10 files changed, 25 insertions(+), 25 deletions(-)
>
> diff --git a/drivers/net/intel/i40e/i40e_ethdev.c b/drivers/net/intel/i40e/i40e_ethdev.c
> index b8ce79061b..799e65ac8d 100644
> --- a/drivers/net/intel/i40e/i40e_ethdev.c
> +++ b/drivers/net/intel/i40e/i40e_ethdev.c
> @@ -5099,15 +5099,15 @@ i40e_res_pool_destroy(struct i40e_res_pool_info *pool)
> return;
>
> for (entry = LIST_FIRST(&pool->alloc_list);
> - entry && (next_entry = LIST_NEXT(entry, next), 1);
> - entry = next_entry) {
> + entry; entry = next_entry) {
The indentation and wrapping seems off here (and similar changes below).
Suggest you see if the whole "for" statement can exist on a single line,
now that it's shorter. If not, keep indentation from original code and
don't adjust it.
Thanks,
/Bruce
> + next_entry = LIST_NEXT(entry, next);
> LIST_REMOVE(entry, next);
> rte_free(entry);
> }
>
<snip>
next prev parent reply other threads:[~2025-11-17 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 8:23 Venkatesh Vemula
2025-11-17 11:54 ` Bruce Richardson [this message]
2025-11-17 11:57 ` Bruce Richardson
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=aRsNC26UxgWgozZb@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aman.deep.singh@bricha3-mobl1.ger.corp.intel.com \
--cc=dev@dpdk.org \
--cc=shaiq.wani@intel.com \
--cc=venkatesh.vemula@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).