From: David Marchand <david.marchand@redhat.com>
To: David Christensen <drc@linux.vnet.ibm.com>
Cc: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
dev <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] eal:ppc: fix incorrect ifdef for ppc_64
Date: Thu, 24 Oct 2019 11:36:50 +0200 [thread overview]
Message-ID: <CAJFAV8zV9aFGzS=v4YfM4CdjLV+6OazHFFsfEfR61WKZbwkhEw@mail.gmail.com> (raw)
In-Reply-To: <632f90cf-c795-d99a-3e18-0138711c00ee@intel.com>
On Thu, Sep 26, 2019 at 9:44 AM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> On 9/25/2019 10:42 PM, David Christensen wrote:
> > An ifdef present in eal_memory.c references "RTE_ARCH_PPC64" when
> > it should actually use "RTE_ARCH_PPC_64". Simple testing revealed
> > that both the PPC_64 and non-PPC_64 versions of the code involved
> > work, but the PPC_64 version of the code is retained to be
> > consistent with other instances in the same file where mmapped
> > memory is accessed in reverse order on Power platforms.
> >
> > Fixes: 66cc45e ("mem: replace memseg with memseg lists")
Cc: stable@dpdk.org
> >
> > Signed-off-by: David Christensen <drc@linux.vnet.ibm.com>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied, thanks.
--
David Marchand
next prev parent reply other threads:[~2019-10-24 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 21:42 David Christensen
2019-09-26 7:43 ` Ferruh Yigit
2019-10-24 9:36 ` David Marchand [this message]
2019-10-16 15:16 ` David Marchand
2019-10-16 20:45 ` David Christensen
2019-10-17 16:18 ` Burakov, Anatoly
2019-10-17 16:35 ` David Marchand
2019-10-17 16:55 ` David Christensen
2019-10-24 7:40 ` David Marchand
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='CAJFAV8zV9aFGzS=v4YfM4CdjLV+6OazHFFsfEfR61WKZbwkhEw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=ferruh.yigit@intel.com \
/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).