DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>, dsosnowski@nvidia.com
Subject: [PATCH 2/2] net/mlx5: fix build with Gcc 15
Date: Sun, 10 Nov 2024 10:41:33 -0800	[thread overview]
Message-ID: <20241110184210.98650-3-stephen@networkplumber.org> (raw)
In-Reply-To: <20241110184210.98650-1-stephen@networkplumber.org>

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>
---
 drivers/net/mlx5/mlx5_flow.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
index 9c43201e05..f8cfa661ec 100644
--- a/drivers/net/mlx5/mlx5_flow.c
+++ b/drivers/net/mlx5/mlx5_flow.c
@@ -8565,7 +8565,7 @@ mlx5_legacy_dmac_flow_create(struct rte_eth_dev *dev, const struct rte_ether_add
 		.hdr.dst_addr = *addr,
 	};
 	struct rte_flow_item_eth unicast_mask = {
-		.hdr.dst_addr.addr_bytes = "\xff\xff\xff\xff\xff\xff",
+		.hdr.dst_addr.addr_bytes = { 0xff, 0xff, 0xff, 0xff, 0xff, 0xff },
 	};
 
 	return mlx5_ctrl_flow(dev, &unicast, &unicast_mask);
@@ -8580,7 +8580,7 @@ mlx5_legacy_dmac_vlan_flow_create(struct rte_eth_dev *dev,
 		.hdr.dst_addr = *addr,
 	};
 	struct rte_flow_item_eth unicast_mask = {
-		.hdr.dst_addr.addr_bytes = "\xff\xff\xff\xff\xff\xff",
+		.hdr.dst_addr.addr_bytes = { 0xff, 0xff, 0xff, 0xff, 0xff, 0xff },
 	};
 	struct rte_flow_item_vlan vlan_spec = {
 		.hdr.vlan_tci = rte_cpu_to_be_16(vid),
-- 
2.45.2


  parent reply	other threads:[~2024-11-10 18:42 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 ` Stephen Hemminger [this message]
2024-11-11  1:47   ` [PATCH 2/2] net/mlx5: " Ferruh Yigit
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=20241110184210.98650-3-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@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).