From: Raslan Darawsheh <rasland@mellanox.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/5] improve mlx5 guide
Date: Tue, 6 Aug 2019 07:59:59 +0000 [thread overview]
Message-ID: <DB3PR0502MB39647E90755AD76577905714C2D50@DB3PR0502MB3964.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20190805153222.29593-1-thomas@monjalon.net>
Hi,
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Thomas Monjalon
> Sent: Monday, August 5, 2019 6:32 PM
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 0/5] improve mlx5 guide
>
> The mlx5 guide is a bit complex. It needs some clean-up in some areas, some
> details are missing, etc.
> This series is a first step of improvement for 19.08.
> More in-depth improvements are expected for 19.11.
>
> Thomas Monjalon (5):
> doc: improve firmware configuration in mlx5 guide
> doc: fix wording and formatting of mlx5 guide
> doc: remove useless console syntax in mlx guides
> doc: add mlx5 design details
> doc: add more details about mlx5 offloads
>
> doc/guides/nics/mlx4.rst | 92 ++++--------- doc/guides/nics/mlx5.rst | 289
> ++++++++++++++++++---------------------
> 2 files changed, 155 insertions(+), 226 deletions(-)
>
> --
> 2.21.0
Series applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2019-08-06 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 15:32 Thomas Monjalon
2019-08-05 15:32 ` [dpdk-dev] [PATCH 1/5] doc: improve firmware configuration in " Thomas Monjalon
2019-08-05 15:32 ` [dpdk-dev] [PATCH 2/5] doc: fix wording and formatting of " Thomas Monjalon
2019-08-05 15:32 ` [dpdk-dev] [PATCH 3/5] doc: remove useless console syntax in mlx guides Thomas Monjalon
2019-08-05 15:32 ` [dpdk-dev] [PATCH 4/5] doc: add mlx5 design details Thomas Monjalon
2019-08-05 15:32 ` [dpdk-dev] [PATCH 5/5] doc: add more details about mlx5 offloads Thomas Monjalon
2019-08-06 7:56 ` [dpdk-dev] [PATCH 0/5] improve mlx5 guide Raslan Darawsheh
2019-08-06 7:59 ` Raslan Darawsheh [this message]
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=DB3PR0502MB39647E90755AD76577905714C2D50@DB3PR0502MB3964.eurprd05.prod.outlook.com \
--to=rasland@mellanox.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).