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:57:15 +0000 [thread overview]
Message-ID: <aRsNm5xke5DD6JwM@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")
Alongside a bugzilla id, we would also expect to see a "fixes" line - or in
this case, multiple fixes lines for each fix. We also would expect a Cc to
stable - though these are low priority fixes we should still flag them as
contenders for backporting.
/Bruce
prev parent reply other threads:[~2025-11-17 11:57 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
2025-11-17 11:57 ` Bruce Richardson [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=aRsNm5xke5DD6JwM@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).