DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dongdong Liu <liudongdong3@huawei.com>
To: Ferruh Yigit <ferruh.yigit@xilinx.com>, <dev@dpdk.org>
Cc: <stable@dpdk.org>, Chengwen Feng <fengchengwen@huawei.com>,
	"Min Hu (Connor)" <humin29@huawei.com>,
	Yisen Zhuang <yisen.zhuang@huawei.com>
Subject: Re: [PATCH 2/2] net/hns3: support backplane media type
Date: Wed, 22 Jun 2022 10:45:39 +0800	[thread overview]
Message-ID: <76dc7719-2cde-9b84-cd1f-c4c8a1fb86c1@huawei.com> (raw)
In-Reply-To: <7e1c673b-5884-44e1-d6f8-5545fe0d15c9@xilinx.com>

Hi Ferruh

Many thanks for your review
On 2022/6/21 20:57, Ferruh Yigit wrote:
> On 6/11/2022 8:42 AM, Dongdong Liu wrote:
>> From: Chengwen Feng<fengchengwen@huawei.com>
>>
>> The 802.11 physical PMA sub-layer defines three media: copper, fiber and
>> backplane. For PMD, the backplane is similar to the fiber, the main
>> differences are that backplane doesn't have optical module.
>>
>> Because the interface of firmware fiber is also applicable to the
>> backplane, this patch supports the backplane only through simple
>> extension.
>>
>> Cc:stable@dpdk.org
>>
>> Signed-off-by: Chengwen Feng<fengchengwen@huawei.com>
>> Signed-off-by: Dongdong Liu<liudongdong3@huawei.com>
>
> What do you think to document new 'backplane' media type support in
> release notes?
Good point, will do.

Thanks,
Dongdong
> .
>

  reply	other threads:[~2022-06-22  2:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11  7:42 [PATCH 0/2] " Dongdong Liu
2022-06-11  7:42 ` [PATCH 1/2] net/hns3: fix fail to obtain VF LSC capability Dongdong Liu
2022-06-24 12:01   ` Ferruh Yigit
2022-06-11  7:42 ` [PATCH 2/2] net/hns3: support backplane media type Dongdong Liu
2022-06-21 12:57   ` Ferruh Yigit
2022-06-22  2:45     ` Dongdong Liu [this message]
2022-06-22  3:09   ` [PATCH V2 " Dongdong Liu
2022-06-22 10:06     ` Ferruh Yigit
2022-06-22 10:29       ` Dongdong Liu
2022-06-22 10:59   ` [PATCH V3 " Dongdong Liu
2022-06-24 12:02     ` Ferruh Yigit

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=76dc7719-2cde-9b84-cd1f-c4c8a1fb86c1@huawei.com \
    --to=liudongdong3@huawei.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@xilinx.com \
    --cc=humin29@huawei.com \
    --cc=stable@dpdk.org \
    --cc=yisen.zhuang@huawei.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).