From: Raslan Darawsheh <rasland@nvidia.com>
To: Gregory Etelson <getelson@nvidia.com>, dev@dpdk.org
Cc: mkashani@nvidia.com, stable@dpdk.org,
Matan Azrad <matan@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Moti Haimovsky <motih@mellanox.com>
Subject: Re: [PATCH 1/2] net/mlx4: fix unnecessary comma compilation warnings
Date: Sun, 2 Nov 2025 09:31:11 +0200 [thread overview]
Message-ID: <7f5d3795-79fd-4438-b982-e8264433ed09@nvidia.com> (raw)
In-Reply-To: <20251029095505.100582-1-getelson@nvidia.com>
Hi
On 29/10/2025 11:55 AM, Gregory Etelson wrote:
> The patch fixes compilation warnings produced by clang -Wcomma option.
>
> Bugzilla ID: 1810
> Fixes: ba576975a89b ("net/mlx4: support hardware TSO")
> Cc: stable@dpdk.org
>
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
Series applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2025-11-02 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 9:55 Gregory Etelson
2025-10-29 9:55 ` [PATCH 2/2] net/mlx5: " Gregory Etelson
2025-10-29 13:29 ` Dariusz Sosnowski
2025-10-29 13:25 ` [PATCH 1/2] net/mlx4: " Dariusz Sosnowski
2025-11-02 7:31 ` Raslan Darawsheh [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=7f5d3795-79fd-4438-b982-e8264433ed09@nvidia.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=motih@mellanox.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.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).