From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, "Bruce Richardson" <bruce.richardson@intel.com>,
"Jerin Jacob" <jerinj@marvell.com>,
"Raslan Darawsheh" <rasland@nvidia.com>,
"David Marchand" <david.marchand@redhat.com>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
"Chengwen Feng" <fengchengwen@huawei.com>,
"Aman Singh" <aman.deep.singh@intel.com>,
"Yuying Zhang" <yuying.zhang@intel.com>,
"Maxime Coquelin" <maxime.coquelin@redhat.com>,
"Chenbo Xia" <chenbo.xia@intel.com>
Subject: Re: [PATCH v2] ethdev: add link speed 400G
Date: Thu, 2 Mar 2023 08:58:41 +0000 [thread overview]
Message-ID: <21a432b8-d4f7-4255-1556-04b4bb2e380a@amd.com> (raw)
In-Reply-To: <CACZ4nhuAvfsNUCQcAH3u=7NpZX5Mb+ptDiQKXSWd7tORP5mXuw@mail.gmail.com>
On 3/1/2023 2:50 PM, Ajit Khaparde wrote:
> On Wed, Mar 1, 2023 at 3:16 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>>
>> There are some devices supporting 400G speed,
>> and it is well standardized in IEEE.
>>
>> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>> Reviewed-by: Morten Brørup <mb@smartsharesystems.com>
>> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>> Acked-by: Chengwen Feng <fengchengwen@huawei.com>
> Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-03-02 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 10:43 [PATCH] " Thomas Monjalon
2023-02-16 10:49 ` Morten Brørup
2023-02-16 11:23 ` Andrew Rybchenko
2023-02-16 11:27 ` fengchengwen
2023-02-16 12:30 ` Ferruh Yigit
2023-02-16 23:56 ` Thomas Monjalon
2023-03-01 11:16 ` [PATCH v2] " Thomas Monjalon
2023-03-01 14:50 ` Ajit Khaparde
2023-03-02 8:58 ` 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=21a432b8-d4f7-4255-1556-04b4bb2e380a@amd.com \
--to=ferruh.yigit@amd.com \
--cc=ajit.khaparde@broadcom.com \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=jerinj@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=mb@smartsharesystems.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=yuying.zhang@intel.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).