From: Shahaf Shuler <shahafs@mellanox.com>
To: Ali Alnubani <alialnu@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 1/2] net/mlx4: fix initialization of struct members
Date: Thu, 15 Nov 2018 08:49:03 +0000 [thread overview]
Message-ID: <DB7PR05MB4426E1BBD5249718D5820806C3DC0@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20181113191039.12720-1-alialnu@mellanox.com>
Tuesday, November 13, 2018 9:11 PM, Ali Alnubani:
> Subject: [PATCH 1/2] net/mlx4: fix initialization of struct members
>
> This patch fixes compilation errors with meson and the clang compiler caused
> by some of the struct members not being initialized.
>
> ```
> ../drivers/net/mlx4/mlx4_mr.c:357:37: error: missing field 'end'
> initializer [-Werror,-Wmissing-field-initializers]
> struct mlx4_mr_cache entry = { 0, };
> ^
> ../drivers/net/mlx4/mlx4_mr.c:401:36: error: missing field 'end'
> initializer [-Werror,-Wmissing-field-initializers]
> struct mlx4_mr_cache ret = { 0, };
> ^
> ../drivers/net/mlx4/mlx4_mr.c:691:35: error: missing field 'end'
> initializer [-Werror,-Wmissing-field-initializers]
> struct mlx4_mr_cache ret = { 0, };
> ^ ```
>
> The compilation errors reproduce with
> clang version 3.4.2 (tags/RELEASE_34/dot2-final) on RHEL.
>
> Fixes: 9797bfcce1c9 ("net/mlx4: add new memory region support")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ali Alnubani <alialnu@mellanox.com>
Series applied to next-net-mlx, thanks.
prev parent reply other threads:[~2018-11-15 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 19:11 Ali Alnubani
2018-11-13 19:11 ` [dpdk-stable] [PATCH 2/2] net/mlx5: " Ali Alnubani
2018-11-14 12:06 ` Shahaf Shuler
2018-11-15 5:50 ` Yongseok Koh
2018-11-15 8:49 ` Shahaf Shuler [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=DB7PR05MB4426E1BBD5249718D5820806C3DC0@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=alialnu@mellanox.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).