From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: "Stanisław Kardach" <kda@semihalf.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
David Christensen <drc@linux.vnet.ibm.com>,
David Marchand <david.marchand@redhat.com>, dev <dev@dpdk.org>,
upstream@semihalf.com, Aaron Conole <aconole@redhat.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Ruifeng Wang (Arm Technology China)" <ruifeng.wang@arm.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: Re: [PATCH 0/3] Fix xmm_t to rte_xmm_t scalar conversion
Date: Tue, 21 Jun 2022 12:48:30 -0700 [thread overview]
Message-ID: <20220621194830.GD18214@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <CALVGJW+KJm3wRNtNo3jmWKqanUpwQfhvYN5-S50=hGotKnoUoA@mail.gmail.com>
On Tue, Jun 21, 2022 at 11:42:55AM +0200, Stanisław Kardach wrote:
> On Tue, Jun 21, 2022 at 11:39 AM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> > <snip>
> > Generally the "cpp" binary is not the c-plus-plus one, but the C
> > preprocessor one. Perhaps the original files are incorrect here, and should
> > all refer to g++.
> >
> > /Bruce
agreed cpp is the preprocessor and one of 2 conventions for file
extension of c++ files (the other being .cc)
conventionally you're looking for CXX i.e. as in env CXX=g++
> >
> That does make sense. I'll submit a separate patchset fixing all
> occurrences (of which there are many).
>
> --
> Best Regards,
> Stanisław Kardach
prev parent reply other threads:[~2022-06-21 19:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 12:16 Stanislaw Kardach
2022-06-09 12:16 ` [PATCH 1/3] eal/riscv: fix xmm_t casting for C++ Stanislaw Kardach
2022-06-13 9:29 ` David Marchand
2022-06-09 12:17 ` [PATCH 2/3] lpm: fix xmm_t casting for C++ in scalar version Stanislaw Kardach
2022-06-13 9:29 ` David Marchand
2022-06-09 12:17 ` [PATCH 3/3] ci: use crossbuild-essential-riscv64 for compiling Stanislaw Kardach
2022-06-13 9:29 ` David Marchand
2022-06-14 12:31 ` Aaron Conole
2022-06-15 7:25 ` [PATCH 0/3] Fix xmm_t to rte_xmm_t scalar conversion David Marchand
2022-06-20 22:54 ` David Christensen
2022-06-21 9:30 ` Stanisław Kardach
2022-06-21 9:38 ` Bruce Richardson
2022-06-21 9:42 ` Stanisław Kardach
2022-06-21 9:49 ` Bruce Richardson
2022-06-21 10:22 ` Thomas Monjalon
2022-06-21 11:05 ` Stanisław Kardach
2022-06-21 11:53 ` Thomas Monjalon
2022-06-21 12:37 ` Stanisław Kardach
2022-06-21 14:20 ` Bruce Richardson
2022-06-21 19:48 ` Tyler Retzlaff [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=20220621194830.GD18214@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=roretzla@linux.microsoft.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=jerinj@marvell.com \
--cc=kda@semihalf.com \
--cc=konstantin.ananyev@intel.com \
--cc=ruifeng.wang@arm.com \
--cc=upstream@semihalf.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).