DPDK patches and discussions
 help / color / mirror / Atom feed

From: Zhangfei Gao <zhangfei.gao@linaro.org>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Cc: Ruifeng Wang <ruifeng.wang@arm.com>,
	Zhangfei Gao <zhangfei.gao@linaro.org>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Elena Agostini <eagostini@nvidia.com>,
	Shepard Siegel <shepard.siegel@atomicrules.com>,
	Ed Czeck <ed.czeck@atomicrules.com>,
	John Miller <john.miller@atomicrules.com>,
	Zyta Szpak <zr@semihalf.com>, Liron Himi <lironh@marvell.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	Satha Rao <skoteshwar@marvell.com>,
	David Hunt <david.hunt@intel.com>
Subject: Re: [PATCH] doc: avoid meson deprecation in setup
Date: Wed, 16 Nov 2022 09:24:17 +0800	[thread overview]
Message-ID: <8fa2f803-f101-5bde-e7d6-a60d4e40f301@linaro.org> (raw)
In-Reply-To: <20221115173516.33051-1-stephen@networkplumber.org>



On 2022/11/16 上午1:35, Stephen Hemminger wrote:
> The command "meson build" causes a deprecation warning with meson 0.64.0.
>                                                                                  WARNING: Running the setup command as `meson [options]` instead of `meson setup [options]` is ambiguous and deprecated.
>
> Therefore fix the examples in the documentation.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>

Thanks Stephen

For doc/guides/cryptodevs/uadk.rst
Acked-by: Zhangfei Gao <zhangfei.gao@linaro.org>

It will be great if updating https://core.dpdk.org/doc/quick-start/ as 
well, here is what I learned from.

Thanks

next prev parent reply	other threads:[~2022-11-16  1:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 17:35 Stephen Hemminger
2022-11-15 17:38 ` Bruce Richardson
2022-11-16  8:24   ` David Marchand
2022-11-16  1:24 ` Zhangfei Gao [this message]
2022-11-17  8:57 ` Ruifeng Wang
2022-11-22 11:37 ` [PATCH v2] " David Marchand
2022-11-22 12:00   ` Stanisław Kardach
2022-11-22 15:20   ` 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=8fa2f803-f101-5bde-e7d6-a60d4e40f301@linaro.org \
    --to=zhangfei.gao@linaro.org \
    --cc=bruce.richardson@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=eagostini@nvidia.com \
    --cc=ed.czeck@atomicrules.com \
    --cc=john.miller@atomicrules.com \
    --cc=kirankumark@marvell.com \
    --cc=lironh@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=ruifeng.wang@arm.com \
    --cc=shepard.siegel@atomicrules.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=stephen@networkplumber.org \
    --cc=zr@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

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).