From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 1/2] doc/freebsd_gsg: add driver guides to document list
Date: Tue, 15 Mar 2022 17:46:38 +0100 [thread overview]
Message-ID: <1698584.X513TT2pbd@thomas> (raw)
In-Reply-To: <20220311200752.1020202-1-bruce.richardson@intel.com>
11/03/2022 21:07, Bruce Richardson:
> The document roadmap section was missing any mention of the individual
> drivers guides which are important for users. Add them to list.
It would be more useful if being links.
You can use the syntax :doc: to link to the start of a doc.
> +* **Driver Reference Guides**: Provides details on each driver inside a particular category.
> + Separate guides exist for each of:
> +
> + * Baseband devices
> +
> + * Compression devices
> +
> + * Cryptographic accelerator devices
> +
> + * DMA devices
> +
> + * Event-based scheduling devices
> +
> + * General purpose GPU devices
> +
> + * Mempool drivers
> +
> + * Network (NIC) devices
> +
> + * "Raw" devices i.e. those not fitting into any other category
> +
> + * Regular expression devices
> +
> + * vDPA (vhost data path acceleration) devices
next prev parent reply other threads:[~2022-03-15 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 20:07 [PATCH 1/2] doc/freebsd_gsg: add driver guides to document list Bruce Richardson
2022-03-11 20:07 ` [PATCH 2/2] doc/freebsd_gsg: update DPDK build section Bruce Richardson
2022-03-15 16:57 ` Thomas Monjalon
2022-03-15 16:46 ` Thomas Monjalon [this message]
2022-03-15 16:52 ` [PATCH 1/2] doc/freebsd_gsg: add driver guides to document list 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=1698584.X513TT2pbd@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.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.