From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev <dev@dpdk.org>, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/4] one more step in makefiles deprecation
Date: Mon, 29 Jun 2020 16:15:04 +0200 [thread overview]
Message-ID: <CAJFAV8xe02Mz+ixCXMfY4_DVf3nhJ=2qf=OxAzuDmSWcbkY-2g@mail.gmail.com> (raw)
In-Reply-To: <20200625214338.1838457-1-thomas@monjalon.net>
On Thu, Jun 25, 2020 at 11:43 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> Some "make" usages are cleaned up in the documentation,
> and an inevitable deprecation warning is printed when using "make".
>
>
> *********************************************
> NOTE: Lots of docs must be converted to meson
> build, configuration and installation layout,
> as soon as possible. Please HELP!
>
> A trick to find some affected docs:
> git grep -- -linux- doc
> *********************************************
>
>
> It should be the final step before complete removal
> of the "make" build system in DPDK 20.11.
>
>
> Thomas Monjalon (4):
> doc: remove outdated guidelines for library addition
> doc: remove build instructions where unneeded
> doc: update build instructions in the Linux guide
> mk: add a paused deprecation warning before each build
>
> doc/guides/bbdevs/fpga_5gnr_fec.rst | 9 +-
> doc/guides/bbdevs/fpga_lte_fec.rst | 9 +-
> doc/guides/cryptodevs/virtio.rst | 9 +-
> .../virtio_user_for_container_networking.rst | 6 -
Lucky guys who got their doc updated, are you expecting a beer from them?
> doc/guides/linux_gsg/build_dpdk.rst | 66 +++--------
> .../linux_gsg/nic_perf_intel_platform.rst | 8 +-
> doc/guides/nics/bnxt.rst | 30 +----
> doc/guides/nics/build_and_test.rst | 43 +------
> doc/guides/prog_guide/extend_dpdk.rst | 109 ------------------
> doc/guides/prog_guide/index.rst | 1 -
> doc/guides/testpmd_app_ug/build_app.rst | 26 -----
> mk/rte.sdkconfig.mk | 5 -
> mk/rte.sdkroot.mk | 16 +++
> 13 files changed, 51 insertions(+), 286 deletions(-)
> delete mode 100644 doc/guides/prog_guide/extend_dpdk.rst
I noticed a warning from FreeBSD shell/read command, could you have a look?
The read command expects a variable name where to store input.
Apart from that, for the series,
Acked-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
next prev parent reply other threads:[~2020-06-29 14:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 0:42 [dpdk-dev] [PATCH " Thomas Monjalon
2020-06-18 0:42 ` [dpdk-dev] [PATCH 1/4] doc: remove outdated guidelines for library addition Thomas Monjalon
2020-06-18 9:46 ` Bruce Richardson
2020-06-18 0:42 ` [dpdk-dev] [PATCH 2/4] doc: remove build instructions where unneeded Thomas Monjalon
2020-06-18 1:10 ` Ajit Khaparde
2020-06-18 2:02 ` Chautru, Nicolas
2020-06-18 8:06 ` Thomas Monjalon
2020-06-18 2:16 ` Zhoujian (jay)
2020-06-18 9:48 ` Bruce Richardson
2020-06-18 0:42 ` [dpdk-dev] [PATCH 3/4] doc: update build instructions in the Linux guide Thomas Monjalon
2020-06-18 0:42 ` [dpdk-dev] [PATCH 4/4] mk: add a paused deprecation warning before each build Thomas Monjalon
2020-06-18 10:04 ` Bruce Richardson
2020-06-18 1:36 ` [dpdk-dev] [PATCH 0/4] one more step in makefiles deprecation Stephen Hemminger
2020-06-25 21:43 ` [dpdk-dev] [PATCH v2 " Thomas Monjalon
2020-06-25 21:43 ` [dpdk-dev] [PATCH v2 1/4] doc: remove outdated guidelines for library addition Thomas Monjalon
2020-06-25 21:43 ` [dpdk-dev] [PATCH v2 2/4] doc: remove build instructions where unneeded Thomas Monjalon
2020-06-25 21:43 ` [dpdk-dev] [PATCH v2 3/4] doc: update build instructions in the Linux guide Thomas Monjalon
2020-06-26 17:11 ` Bruce Richardson
2020-06-25 21:43 ` [dpdk-dev] [PATCH v2 4/4] mk: add a paused deprecation warning before each build Thomas Monjalon
2020-06-29 14:15 ` David Marchand [this message]
2020-06-29 14:26 ` [dpdk-dev] [PATCH v2 0/4] one more step in makefiles deprecation Thomas Monjalon
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='CAJFAV8xe02Mz+ixCXMfY4_DVf3nhJ=2qf=OxAzuDmSWcbkY-2g@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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).