DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: 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>, nd <nd@arm.com>
Subject: RE: [PATCH] doc: avoid meson deprecation in setup
Date: Thu, 17 Nov 2022 08:57:18 +0000	[thread overview]
Message-ID: <AS8PR08MB708019CBDCB16D9BD40600019E069@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20221115173516.33051-1-stephen@networkplumber.org>

> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Wednesday, November 16, 2022 1:35 AM
> To: dev@dpdk.org
> Cc: Stephen Hemminger <stephen@networkplumber.org>; 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: [PATCH] doc: avoid meson deprecation in setup
> 
> 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>
> ---
>  doc/guides/cryptodevs/armv8.rst                  |  2 +-
>  doc/guides/cryptodevs/uadk.rst                   |  2 +-
>  doc/guides/freebsd_gsg/build_dpdk.rst            |  2 +-
>  doc/guides/gpus/cuda.rst                         |  4 ++--
>  doc/guides/howto/openwrt.rst                     |  4 ++--
>  doc/guides/nics/ark.rst                          |  2 +-
>  doc/guides/nics/mvneta.rst                       |  2 +-
>  doc/guides/nics/mvpp2.rst                        |  2 +-
>  doc/guides/platform/bluefield.rst                |  4 ++--
>  doc/guides/platform/cnxk.rst                     |  4 ++--
>  doc/guides/platform/octeontx.rst                 |  8 ++++----
>  doc/guides/prog_guide/build-sdk-meson.rst        |  4 ++--
>  doc/guides/prog_guide/lto.rst                    |  2 +-
>  doc/guides/prog_guide/profile_app.rst            |  2 +-
>  doc/guides/sample_app_ug/vm_power_management.rst | 14 ++++++--------
>  15 files changed, 28 insertions(+), 30 deletions(-)
> 
> diff --git a/doc/guides/cryptodevs/armv8.rst b/doc/guides/cryptodevs/armv8.rst index
> 8963f66a206c..1a006754cbe4 100644
> --- a/doc/guides/cryptodevs/armv8.rst
> +++ b/doc/guides/cryptodevs/armv8.rst

Change looks good to me. Thanks.
Some occurrences in doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst need update as well.


  parent reply	other threads:[~2022-11-17  8:57 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
2022-11-17  8:57 ` Ruifeng Wang [this message]
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=AS8PR08MB708019CBDCB16D9BD40600019E069@AS8PR08MB7080.eurprd08.prod.outlook.com \
    --to=ruifeng.wang@arm.com \
    --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=nd@arm.com \
    --cc=ndabilpuram@marvell.com \
    --cc=shepard.siegel@atomicrules.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=stephen@networkplumber.org \
    --cc=zhangfei.gao@linaro.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
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).