From: Bruce Richardson <bruce.richardson@intel.com>
To: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
Cc: maxime.coquelin@redhat.com, chenbo.xia@intel.com, dev@dpdk.org
Subject: Re: [PATCH 1/3] examples/vhost: update makefile to match meson build system
Date: Fri, 10 Jun 2022 13:05:12 +0100 [thread overview]
Message-ID: <YqMzeHeGd+D5rJaR@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20220607114856.1085803-1-herakliusz.lipiec@intel.com>
On Tue, Jun 07, 2022 at 12:48:54PM +0100, Herakliusz Lipiec wrote:
> Meson build system creates a vhost binary but Makefile
> and docs reference same as vhost-switch. Updating makefile
> to match meson.
>
> Signed-off-by: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
> ---
> examples/vhost/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/examples/vhost/Makefile b/examples/vhost/Makefile
> index 975a5dfe40..ea64f02bb0 100644
> --- a/examples/vhost/Makefile
> +++ b/examples/vhost/Makefile
> @@ -2,7 +2,7 @@
> # Copyright(c) 2010-2014 Intel Corporation
>
> # binary name
> -APP = vhost-switch
> +APP = dpdk-vhost
>
> # all source are stored in SRCS-y
> SRCS-y := main.c virtio_net.c
> --
While I see the docs are updated in the next patch, I think it would be
good to have the doc binary renames included here for completeness.
With this addition:
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
next prev parent reply other threads:[~2022-06-10 12:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 11:48 Herakliusz Lipiec
2022-06-07 11:48 ` [PATCH 2/3] doc: update vhost sample app docs Herakliusz Lipiec
2022-06-20 1:56 ` Xia, Chenbo
2022-06-07 11:48 ` [PATCH 3/3] examples/vhost: update vhost usage message Herakliusz Lipiec
2022-06-20 1:59 ` Xia, Chenbo
2022-06-10 12:05 ` Bruce Richardson [this message]
2022-06-21 12:11 ` [PATCH 1/3] examples/vhost: update makefile to match meson build system Herakliusz Lipiec
2022-06-21 12:13 ` [PATCH v2 " Herakliusz Lipiec
2022-06-21 12:13 ` [PATCH v2 2/3] doc: update vhost sample app docs Herakliusz Lipiec
2022-06-21 12:13 ` [PATCH v2 3/3] examples/vhost: update vhost usage message Herakliusz Lipiec
2022-06-21 13:12 ` [PATCH v2 1/3] examples/vhost: update makefile to match meson build system Xia, Chenbo
2022-06-21 15:20 ` [PATCH v3 " Herakliusz Lipiec
2022-06-21 15:20 ` [PATCH v3 2/3] doc: update vhost sample app docs Herakliusz Lipiec
2022-07-01 13:10 ` Xia, Chenbo
2022-07-01 13:53 ` Maxime Coquelin
2022-06-21 15:20 ` [PATCH v3 3/3] examples/vhost: update vhost usage message Herakliusz Lipiec
2022-07-01 13:53 ` Maxime Coquelin
2022-07-01 13:40 ` [PATCH v3 1/3] examples/vhost: update makefile to match meson build system Maxime Coquelin
2022-07-01 13:53 ` Maxime Coquelin
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=YqMzeHeGd+D5rJaR@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=herakliusz.lipiec@intel.com \
--cc=maxime.coquelin@redhat.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).