From: Thomas Monjalon <thomas@monjalon.net>
To: Ruifeng Wang <ruifeng.wang@arm.com>
Cc: dev@dpdk.org, honnappa.nagarahalli@arm.com, nd@arm.com,
Haiyue Wang <haiyue.wang@intel.com>,
jerinj@marvell.com, stable@dpdk.org, david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH 0/2] gcc build fix
Date: Fri, 27 Nov 2020 17:03:45 +0100 [thread overview]
Message-ID: <40479894.kOOi6BpvtO@thomas> (raw)
In-Reply-To: <20201127080903.26817-1-ruifeng.wang@arm.com>
27/11/2020 09:09, Ruifeng Wang:
> This series fixed issues found when building project
> with Gcc '-O0' option.
>
> Ruifeng Wang (2):
> eal/arm: fix gcc build for optimization level 0
> net/igc: fix gcc build for optimization level 0
Series v1 applied with Cc:stable, thanks.
prev parent reply other threads:[~2020-11-27 16:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 8:09 [dpdk-dev] [PATCH 0/2] gcc build fix Ruifeng Wang
2020-11-27 8:09 ` [dpdk-dev] [PATCH 1/2] eal/arm: fix gcc build for optimization level 0 Ruifeng Wang
2020-11-27 8:39 ` David Marchand
2020-11-27 8:51 ` Jerin Jacob
2020-11-27 9:25 ` David Marchand
2020-11-27 9:33 ` Jerin Jacob
2020-11-27 9:45 ` David Marchand
2020-11-27 10:05 ` Ruifeng Wang
2020-11-27 10:28 ` Jerin Jacob
2020-11-27 9:39 ` Andrew Rybchenko
2020-11-27 9:36 ` Ruifeng Wang
2020-11-27 8:09 ` [dpdk-dev] [PATCH 2/2] net/igc: " Ruifeng Wang
2020-11-27 8:53 ` Jerin Jacob
2020-11-27 9:02 ` David Marchand
2020-11-27 12:13 ` David Marchand
2020-11-27 14:50 ` Wang, Haiyue
2020-11-27 10:15 ` [dpdk-dev] [PATCH v2 0/2] gcc build fix Ruifeng Wang
2020-11-27 10:15 ` [dpdk-dev] [PATCH v2 1/2] eal/arm: fix gcc build for optimization level 0 Ruifeng Wang
2020-11-27 13:03 ` Ruifeng Wang
2020-11-27 10:15 ` [dpdk-dev] [PATCH v2 2/2] net/igc: " Ruifeng Wang
2020-11-27 13:35 ` [dpdk-dev] [PATCH v2 0/2] gcc build fix Thomas Monjalon
2020-11-27 14:08 ` Ruifeng Wang
2020-11-27 16:03 ` 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=40479894.kOOi6BpvtO@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.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 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.