All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: dev@dpdk.org, cristian.dumitrescu@intel.com, aconole@redhat.com,
	ci@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] pipeline: fix build with gcc 4.8.5
Date: Wed, 21 Apr 2021 12:41:47 +0200	[thread overview]
Message-ID: <9470563.utI7u1ruXk@thomas> (raw)
In-Reply-To: <20210421100638.19451-1-alialnu@nvidia.com>

21/04/2021 12:06, Ali Alnubani:
> Compilation on CentOS 7 with gcc version 4.8.5 fails with
> the following errors:
> ```
> ...
> error: 'src_struct_id' may be used uninitialized in this
> function [-Werror=maybe-uninitialized]
> ...
> error: 'dst_struct_id' may be used uninitialized in this
> function [-Werror=maybe-uninitialized]
> ...
> ```
> 
> This patch fixes the build errors by initializing both variables.
> 
> Bugzilla ID: 683
> Fixes: 783768136f29 ("pipeline: auto-detect endianness of action arguments")
> Cc: cristian.dumitrescu@intel.com

This patch was depending on others so CI didn't run.
I've requested a partial CI run when dependencies resolved and it passed.
That's what happens when I merge a patch without a re-run of the full CI.
We really need to be able to re-run CI easily,
plus managing the dependencies in the CI.

> Signed-off-by: Ali Alnubani <alialnu@nvidia.com>

Applied, thanks




      reply	other threads:[~2021-04-21 10:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 10:06 [dpdk-dev] [PATCH] pipeline: fix build with gcc 4.8.5 Ali Alnubani
2021-04-21 10:41 ` Thomas Monjalon [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=9470563.utI7u1ruXk@thomas \
    --to=thomas@monjalon.net \
    --cc=aconole@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=ci@dpdk.org \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.