DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Asaf Penso <asafp@mellanox.com>,
	thomas@monjalon.net, arybchenko@solarflare.com,
	viacheslavo@mellanox.com, matan@mellanox.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] net/mlx5: add 200G link speed
Date: Wed, 6 May 2020 21:24:56 +0100	[thread overview]
Message-ID: <58f88ad9-bbec-789f-6ffd-bc66b98263bf@intel.com> (raw)
In-Reply-To: <1588767728-5722-1-git-send-email-asafp@mellanox.com>

On 5/6/2020 1:22 PM, Asaf Penso wrote:
> There is no way to report back a link speed of 200Gbps.
> 
> Adding 200G link speed.
> 
> Signed-off-by: Asaf Penso <asafp@mellanox.com>

The doc warning fixed [1] and patch split into two as discussed [2] while merging.

For ethdev part,
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/master, thanks.


[1]
WARNING: Inline strong start-string without end-string.

[2]
ethdev: add 200G link speed
net/mlx5: support 200G link speed

      parent reply	other threads:[~2020-05-06 20:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 13:44 [dpdk-dev] [PATCH] net/mlx5: add 200G and 400G " Asaf Penso
2020-04-22 16:29 ` Ajit Khaparde
2020-05-06 10:58 ` [dpdk-dev] [PATCH v2] net/mlx5: add 200G " Asaf Penso
2020-05-06 12:07   ` [dpdk-dev] [PATCH v3] " Asaf Penso
2020-05-06 13:43     ` Slava Ovsiienko
2020-05-06 12:22   ` Asaf Penso
2020-05-06 12:59     ` Ferruh Yigit
2020-05-06 13:17       ` Thomas Monjalon
2020-05-06 14:01         ` Ferruh Yigit
2020-05-06 14:19           ` Thomas Monjalon
2020-05-06 14:22             ` Ferruh Yigit
2020-05-06 14:23               ` Asaf Penso
2020-05-06 20:24     ` Ferruh Yigit [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=58f88ad9-bbec-789f-6ffd-bc66b98263bf@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=arybchenko@solarflare.com \
    --cc=asafp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@mellanox.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).