From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] doc/guides: fix reference to x32 architecture
Date: Thu, 22 Oct 2020 10:32:30 +0200 [thread overview]
Message-ID: <CAJFAV8zOE5=t9igcOMSHJ87JrVXy3WQzDtu0cQBtOfFr5Pi81Q@mail.gmail.com> (raw)
In-Reply-To: <20201022082552.GE83@bricha3-MOBL.ger.corp.intel.com>
On Thu, Oct 22, 2020 at 10:26 AM Bruce Richardson
<bruce.richardson@intel.com> wrote:
> > diff --git a/doc/guides/contributing/design.rst b/doc/guides/contributing/design.rst
> > index 5fe7f63942..54dad08846 100644
> > --- a/doc/guides/contributing/design.rst
> > +++ b/doc/guides/contributing/design.rst
> > @@ -47,7 +47,7 @@ Per Architecture Sources
> > The following config options can be used:
> >
> > * ``CONFIG_RTE_ARCH`` is a string that contains the name of the architecture.
> > -* ``CONFIG_RTE_ARCH_I686``, ``CONFIG_RTE_ARCH_X86_64``, ``CONFIG_RTE_ARCH_X86_64_32`` or ``CONFIG_RTE_ARCH_PPC_64`` are defined only if we are building for those architectures.
> > +* ``CONFIG_RTE_ARCH_I686``, ``CONFIG_RTE_ARCH_X86_64``, ``CONFIG_RTE_ARCH_X86_X32`` or ``CONFIG_RTE_ARCH_PPC_64`` are defined only if we are building for those architectures.
> >
>
> With make gone, I don't believe that there is an RTE_ARCH_X86_X32 now
> either.
As Thomas pointed offlist, this should go with Ciara series anyway.
I'll drop this patch.
--
David Marchand
prev parent reply other threads:[~2020-10-22 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 8:01 David Marchand
2020-10-22 8:25 ` Bruce Richardson
2020-10-22 8:32 ` David Marchand [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='CAJFAV8zOE5=t9igcOMSHJ87JrVXy3WQzDtu0cQBtOfFr5Pi81Q@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).