From: Stephen Hemminger <stephen@networkplumber.org>
To: ohilyard@iol.unh.edu
Cc: dev@dpdk.org, Honnappa.Nagarahalli@arm.com, thomas@monjalon.net
Subject: Re: [PATCH v1 1/4] app/test-pmd-api: Add C++ Compiler
Date: Mon, 2 Oct 2023 11:33:01 -0700 [thread overview]
Message-ID: <20231002113301.0d188d6f@hermes.local> (raw)
In-Reply-To: <20220407214707.29730-2-ohilyard@iol.unh.edu>
On Thu, 7 Apr 2022 17:47:05 -0400
ohilyard@iol.unh.edu wrote:
> From: Owen Hilyard <ohilyard@iol.unh.edu>
>
> Adds a C++ compiler to the project, which is currently enabled by
> default for ease of testing. Meson currently lacks a way to try to get a
> compiler, and failing to find a compiler for a language always causes a
> hard error, so this is the only workable approach.
>
> Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
This patch has a problem.
What ever editor you used failed to add a end of line (newline)
on the last line of the file. Git accepts this but complains, other tools
do not handle it well.
Pleas rebase and fix the series.
next prev parent reply other threads:[~2023-10-02 18:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 21:47 [PATCH v1 0/4] [RFC] Testpmd RPC API ohilyard
2022-04-07 21:47 ` [PATCH v1 1/4] app/test-pmd-api: Add C++ Compiler ohilyard
2023-10-02 18:33 ` Stephen Hemminger [this message]
2022-04-07 21:47 ` [PATCH v1 2/4] app/test-pmd-api: Add POC with gRPC deps ohilyard
2022-04-07 21:47 ` [PATCH v1 3/4] app/test-pmd-api: Add protobuf file ohilyard
2022-04-07 21:47 ` [PATCH v1 4/4] app/test-pmd-api: Implementation files for the API ohilyard
2022-04-11 14:27 ` [PATCH v1 0/4] [RFC] Testpmd RPC API Jerin Jacob
2022-04-11 17:48 ` Owen Hilyard
2022-04-12 6:07 ` Jerin Jacob
2022-04-13 12:47 ` Owen Hilyard
2022-04-14 12:07 ` Ananyev, Konstantin
2022-04-14 20:09 ` Owen Hilyard
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=20231002113301.0d188d6f@hermes.local \
--to=stephen@networkplumber.org \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=ohilyard@iol.unh.edu \
--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).