From: Bruce Richardson <bruce.richardson@intel.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: David Young <dave@youngcopy.com>, <dev@dpdk.org>
Subject: Re: [PATCH 5/6] Section 5: Appendix
Date: Mon, 25 Sep 2023 13:24:04 +0100 [thread overview]
Message-ID: <ZRF75KE9oLGwvOPz@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <2d67e056-8020-4153-9494-08c264496254@amd.com>
On Mon, Sep 25, 2023 at 12:33:52PM +0100, Ferruh Yigit wrote:
> On 9/20/2023 4:48 PM, David Young wrote:
> > ---
> > .../appendix/cross_compile_dpdk.rst | 37 +++
> > .../appendix/dpdk_meson_build_options.rst | 57 ++++
> > .../getting_started_guide/appendix/index.rst | 17 +
> > .../running_dpdk_apps_without_root.rst | 36 +++
> > .../appendix/vfio_advanced.rst | 295 ++++++++++++++++++
> > 5 files changed, 442 insertions(+)
> > create mode 100644 doc/guides/getting_started_guide/appendix/cross_compile_dpdk.rst
> > create mode 100644 doc/guides/getting_started_guide/appendix/dpdk_meson_build_options.rst
> > create mode 100644 doc/guides/getting_started_guide/appendix/index.rst
> > create mode 100644 doc/guides/getting_started_guide/appendix/running_dpdk_apps_without_root.rst
> > create mode 100644 doc/guides/getting_started_guide/appendix/vfio_advanced.rst
> >
>
> These files are put under 'appendix' folder,
> and I can see these documents are linked from other 'getting started
> guide' documentations, which I assume the reason to put these under
> 'appendix' folder.
> But these are not limited to getting started, perhaps we can do a better
> organization of them out of getting started appendix.
>
The plan is to merge all three GSG docs into one, in which case the single
combined GSG should be the only thing referencing these. Therefore, I think
having them placed as here makes most sense.
/Bruce
next prev parent reply other threads:[~2023-09-25 12:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 15:48 [PATCH 0/6] docs: Unify Getting Started Guides David Young
2023-09-20 15:48 ` [PATCH 1/6] Section 1: Introduction David Young
2023-09-25 11:30 ` Ferruh Yigit
2023-10-11 18:26 ` Dave Young
2023-09-20 15:48 ` [PATCH 2/6] Section 2: Install and Build DPDK David Young
2023-09-25 11:30 ` Ferruh Yigit
2023-09-25 12:20 ` Bruce Richardson
2023-09-25 16:05 ` Tyler Retzlaff
2023-10-12 18:08 ` Dave Young
2023-10-17 13:37 ` Tyler Retzlaff
2023-09-20 15:48 ` [PATCH 3/6] Section 3: Setting up a System to Run DPDK Applications David Young
2023-09-25 11:31 ` Ferruh Yigit
2023-09-25 12:22 ` Bruce Richardson
2023-10-12 17:32 ` Dave Young
2023-09-20 15:48 ` [PATCH 4/6] Section 4: Running Applications David Young
2023-09-25 11:32 ` Ferruh Yigit
2023-09-20 15:48 ` [PATCH 5/6] Section 5: Appendix David Young
2023-09-25 11:33 ` Ferruh Yigit
2023-09-25 11:52 ` Ferruh Yigit
2023-09-25 12:24 ` Bruce Richardson [this message]
2023-09-20 15:48 ` [PATCH 6/6] Section 6: Glossary David Young
2023-09-25 11:43 ` Ferruh Yigit
2023-09-22 4:15 ` [PATCH 0/6] docs: Unify Getting Started Guides Tyler Retzlaff
2023-09-22 14:47 ` David Marchand
2023-09-22 15:54 ` Bruce Richardson
2023-09-25 11:54 ` Ferruh Yigit
2023-10-11 18:34 ` Dave Young
2023-10-13 16:28 ` Bruce Richardson
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=ZRF75KE9oLGwvOPz@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dave@youngcopy.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.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).