patches for DPDK stable branches
 help / color / mirror / Atom feed
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-stable] [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.



           reply	other threads:[~2020-11-27 16:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20201127080903.26817-1-ruifeng.wang@arm.com>]

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 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).