From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Cc: dsosnowski@nvidia.com
Subject: Re: [PATCH 2/2] net/mlx5: fix build with Gcc 15
Date: Mon, 11 Nov 2024 01:47:16 +0000 [thread overview]
Message-ID: <5e7ede47-6c92-4509-a075-5d28c4517e98@amd.com> (raw)
In-Reply-To: <20241110184210.98650-3-stephen@networkplumber.org>
On 11/10/2024 6:41 PM, Stephen Hemminger wrote:
> Fixes warnings from Gcc 15 about using string for initialization.
> ../drivers/net/mlx5/mlx5_flow.c: In function ‘mlx5_legacy_dmac_flow_create’:
> ../drivers/net/mlx5/mlx5_flow.c:8568:44: warning: initializer-string for array of ‘unsigned char’ is too long [-Wunterminated-string-initialization]
> 8568 | .hdr.dst_addr.addr_bytes = "\xff\xff\xff\xff\xff\xff",
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> ../drivers/net/mlx5/mlx5_flow.c: In function ‘mlx5_legacy_dmac_vlan_flow_create’:
> ../drivers/net/mlx5/mlx5_flow.c:8583:44: warning: initializer-string for array of ‘unsigned char’ is too long [-Wunterminated-string-initialization]
> 8583 | .hdr.dst_addr.addr_bytes = "\xff\xff\xff\xff\xff\xff",
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Fixes: cf99567fe566 ("net/mlx5: add legacy unicast flow rules management")
> Cc: dsosnowski@nvidia.com
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
Dariusz already sent a fix before, will get it:
https://patches.dpdk.org/project/dpdk/patch/20241108160724.730989-1-dsosnowski@nvidia.com/
next prev parent reply other threads:[~2024-11-11 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 18:41 [PATCH 0/2] Build with Gcc 15 fixes Stephen Hemminger
2024-11-10 18:41 ` [PATCH 1/2] net/dpaa2: fix build with Gcc 15 Stephen Hemminger
2024-11-11 1:47 ` Ferruh Yigit
2024-11-10 18:41 ` [PATCH 2/2] net/mlx5: " Stephen Hemminger
2024-11-11 1:47 ` Ferruh Yigit [this message]
2024-11-11 8:12 ` [PATCH 0/2] Build with Gcc 15 fixes Morten Brørup
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=5e7ede47-6c92-4509-a075-5d28c4517e98@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=stephen@networkplumber.org \
/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).