From: Thomas Monjalon <thomas@monjalon.net>
To: David Young <dave@youngcopy.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
Aaron Conole <aconole@redhat.com>
Subject: Re: [PATCH v4 0/6] docs: getting started guide consolidation
Date: Fri, 01 Dec 2023 16:17:43 +0100 [thread overview]
Message-ID: <25541050.hxa6pUQ8Du@thomas> (raw)
In-Reply-To: <20231123012633.2005-1-dave@youngcopy.com>
23/11/2023 02:26, David Young:
> .../appendix/cross_compile_dpdk.rst | 37 +++
> .../appendix/dpdk_meson_build_options.rst | 57 ++++
> .../hugepages_different_architectures.rst | 56 ++++
> .../getting_started_guide/appendix/index.rst | 18 ++
> .../running_dpdk_apps_without_root.rst | 24 ++
> .../appendix/vfio_advanced.rst | 301 ++++++++++++++++++
> doc/guides/getting_started_guide/glossary.rst | 78 +++++
> doc/guides/getting_started_guide/index.rst | 18 ++
> .../building_from_sources.rst | 180 +++++++++++
> .../install_and_build/index.rst | 14 +
> .../installing_prebuilt_packages.rst | 54 ++++
> doc/guides/getting_started_guide/intro.rst | 13 +
> doc/guides/getting_started_guide/run_apps.rst | 114 +++++++
> .../getting_started_guide/run_apps/index.rst | 10 +
> .../run_apps/run_apps.rst | 118 +++++++
> .../getting_started_guide/system_setup.rst | 197 ++++++++++++
> doc/guides/index.rst | 1 +
> 17 files changed, 1290 insertions(+)
I suppose we should also remove the old guide at the same time, isn't it?
next prev parent reply other threads:[~2023-12-01 15:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 4:01 [PATCH v3 0/7] docs: getting started guide consolidation David Young
2023-11-03 4:01 ` [PATCH v3 1/7] Section 1: Introduction David Young
2023-11-03 13:11 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 2/7] Section 2: Install and Build DPDK David Young
2023-11-03 13:55 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 3/7] Section 3: Setting up a System to Run DPDK Applications David Young
2023-11-03 14:17 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 4/7] Section 4: Running Applications David Young
2023-11-03 15:13 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 5/7] Section 5: Appendix David Young
2023-11-03 15:23 ` Bruce Richardson
2023-11-16 1:28 ` Dave Young
2023-11-17 13:04 ` Bruce Richardson
2023-11-03 4:01 ` [PATCH v3 6/7] Added link to Getting Started Guide in index.rst David Young
2023-11-03 13:32 ` Bruce Richardson
2023-11-03 14:22 ` Bruce Richardson
2023-11-08 1:47 ` Dave Young
2023-11-08 2:06 ` Dave Young
2023-11-03 4:01 ` [PATCH v3 7/7] Section 6: Glossary David Young
2023-11-03 15:26 ` Bruce Richardson
2023-11-23 1:26 ` [PATCH v4 0/6] docs: getting started guide consolidation David Young
2023-11-23 1:26 ` [PATCH v4 1/6] Section 1: Introduction David Young
2023-11-23 1:26 ` [PATCH v4 2/6] Section 2: Install and Build DPDK David Young
2023-11-23 1:26 ` [PATCH v4 3/6] Section 3: Setting up a System to Run DPDK Applications David Young
2023-11-23 1:26 ` [PATCH v4 4/6] Section 4: Running Applications David Young
2023-11-23 1:26 ` [PATCH v4 5/6] Section 5: Appendix David Young
2023-11-23 1:26 ` [PATCH v4 6/6] Section 6: Glossary David Young
2024-09-11 15:54 ` Stephen Hemminger
2024-09-11 15:55 ` Stephen Hemminger
2023-12-01 15:17 ` Thomas Monjalon [this message]
2024-10-04 16:29 ` [PATCH v4 0/6] docs: getting started guide consolidation Stephen Hemminger
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=25541050.hxa6pUQ8Du@thomas \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dave@youngcopy.com \
--cc=dev@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.