patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: luca.boccassi@gmail.com
Cc: stable@dpdk.org, Luca Boccassi <bluca@debian.org>
Subject: Re: [PATCH 19.11 20.11] pmdinfogen: fix compilation with Clang 3.4.2 on CentOS 7
Date: Wed, 30 Mar 2022 14:51:49 +0200	[thread overview]
Message-ID: <CAATJJ0KSKqAcphBBJrH-xTENJOfYQRcaCVJKvE==q=XT=JV1oA@mail.gmail.com> (raw)
In-Reply-To: <20220330121225.322838-1-luca.boccassi@gmail.com>

On Wed, Mar 30, 2022 at 2:13 PM <luca.boccassi@gmail.com> wrote:
>
> From: Luca Boccassi <bluca@debian.org>
>
> $ meson --werror --buildtype=debugoptimized build && ninja-build -C build
> [..]
> [5/2516] Compiling C object buildtools/pmdinfogen/pmdinfogen.p/pmdinfogen.c.o
> FAILED: buildtools/pmdinfogen/pmdinfogen.p/pmdinfogen.c.o
> clang -Ibuildtools/pmdinfogen/pmdinfogen.p -Ibuildtools/pmdinfogen -I../../root/dpdk/buildtools/pmdinfogen -I. -I../../root/dpdk -Iconfig -I../../root/dpdk/config -Ilib/librte_eal/include -I../../root/dpdk/lib/librte_eal/include -Ilib/librte_eal/linux/include -I../../root/dpdk/lib/librte_eal/linux/include -Ilib/librte_eal/x86/include -I../../root/dpdk/lib/librte_eal/x86/include -Ilib/librte_pci -I../../root/dpdk/lib/librte_pci -Xclang -fcolor-diagnostics -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -O2 -g -MD -MQ buildtools/pmdinfogen/pmdinfogen.p/pmdinfogen.c.o -MF buildtools/pmdinfogen/pmdinfogen.p/pmdinfogen.c.o.d -o buildtools/pmdinfogen/pmdinfogen.p/pmdinfogen.c.o -c ../../root/dpdk/buildtools/pmdinfogen/pmdinfogen.c
> ../../root/dpdk/buildtools/pmdinfogen/pmdinfogen.c:431:27: error: missing field 'hdr' initializer [-Werror,-Wmissing-field-initializers]
>         struct elf_info info = {0};
>                                  ^
> 1 error generated.
> [..]

The change itself LGTM and works on my end for 19.11 (applied it).

Maybe adding a fixes: 0decf84217f1ef8af132948a0661559a96961495 ?

With or without it is fine,
Reviewed-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>

> Use structured initialization
>
> Bugzilla ID: 984
>
> Signed-off-by: Luca Boccassi <bluca@debian.org>
> ---
>  buildtools/pmdinfogen/pmdinfogen.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/buildtools/pmdinfogen/pmdinfogen.c b/buildtools/pmdinfogen/pmdinfogen.c
> index a68d1ea999..534ed9f3c8 100644
> --- a/buildtools/pmdinfogen/pmdinfogen.c
> +++ b/buildtools/pmdinfogen/pmdinfogen.c
> @@ -428,7 +428,7 @@ static void output_pmd_info_string(struct elf_info *info, char *outfile)
>
>  int main(int argc, char **argv)
>  {
> -       struct elf_info info = {0};
> +       struct elf_info info = {};
>         int rc = 1;
>
>         if (argc < 3) {
> --
> 2.34.1
>


-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

  reply	other threads:[~2022-03-30 12:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 12:12 luca.boccassi
2022-03-30 12:51 ` Christian Ehrhardt [this message]
2022-03-30 14:12 ` [PATCH 19.11 20.11 v2] " luca.boccassi
2022-04-01  8:15   ` Christian Ehrhardt

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='CAATJJ0KSKqAcphBBJrH-xTENJOfYQRcaCVJKvE==q=XT=JV1oA@mail.gmail.com' \
    --to=christian.ehrhardt@canonical.com \
    --cc=bluca@debian.org \
    --cc=luca.boccassi@gmail.com \
    --cc=stable@dpdk.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).