From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: Re: [PATCH 3/4] doc: rework mlx5 guide per features
Date: Fri, 18 Jul 2025 08:20:51 -0700 [thread overview]
Message-ID: <20250718082051.53534122@hermes.local> (raw)
In-Reply-To: <20250717220912.376503-4-thomas@monjalon.net>
On Fri, 18 Jul 2025 00:05:43 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> The documentation for net mlx5 is reworded and re-organized.
> Design, configuration, requirements and limitations
> are grouped per features for easier reading.
>
> New details are added, and more will come later.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
Fix spelling errors (found by checkpatch).
Other than that looks good.
next prev parent reply other threads:[~2025-07-18 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 22:05 [PATCH 0/4] rework mlx5 guide Thomas Monjalon
2025-07-17 22:05 ` [PATCH 1/4] doc: simplify mlx5 devices lists Thomas Monjalon
2025-07-17 22:05 ` [PATCH 2/4] doc: add table styles for guides Thomas Monjalon
2025-07-17 22:05 ` [PATCH 3/4] doc: rework mlx5 guide per features Thomas Monjalon
2025-07-18 15:20 ` Stephen Hemminger [this message]
2025-07-17 22:05 ` [PATCH 4/4] doc: add testpmd command examples in mlx5 guide Thomas Monjalon
2025-07-18 15:36 ` [PATCH 0/4] rework " Stephen Hemminger
2025-07-19 0:21 ` Thomas Monjalon
2025-07-19 1:48 ` 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=20250718082051.53534122@hermes.local \
--to=stephen@networkplumber.org \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.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 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.