DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Lijun Ou <oulijun@huawei.com>,
	thomas@monjalon.net, arybchenko@solarflare.com
Cc: dev@dpdk.org, linuxarm@openeuler.org
Subject: Re: [dpdk-dev] [PATCH v3 0/3] update doc for hns3
Date: Wed, 3 Feb 2021 09:43:36 +0000	[thread overview]
Message-ID: <644181ec-5f4c-c2a4-12c5-c5a2428b61e8@intel.com> (raw)
In-Reply-To: <465f2f3e-e4f6-164f-b09a-cc5eeca6a0db@intel.com>

On 1/29/2021 11:57 AM, Ferruh Yigit wrote:
> On 1/29/2021 9:22 AM, Lijun Ou wrote:
>> Here series add some updates for hns3 rst and TM feature
>> note for hns3 as well as FEC feature notes.
>>
>> v3:
>> 1. merge patch[2/3] into patch[1] base on v2
>> 2. fix some format errors
>>
>> v2:
>> 1. fix a meson build warning for patch[4/5]
>> 2. add a new patch for update hns3.ini and cxgbe.ini
>> 3. add Fixes for all patches.
>>
>> Lijun Ou (2):
>>    doc: update release notes for hns3
>>    doc: fix hns3 rst
>>
>> Min Hu (Connor) (1):
>>    doc: add FEC in NIC features
>>
> 
> For series,
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Series applied to dpdk-next-net/main, thanks.

      reply	other threads:[~2021-02-03  9:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 13:43 [dpdk-dev] [PATCH " Lijun Ou
2021-01-20 13:43 ` [dpdk-dev] [PATCH 1/3] doc: add FEC in NIC features Lijun Ou
2021-01-28  0:20   ` Ferruh Yigit
2021-01-28  0:21     ` Ferruh Yigit
2021-01-28  1:55     ` oulijun
2021-01-28  9:14       ` Thomas Monjalon
2021-01-20 13:43 ` [dpdk-dev] [PATCH 2/3] doc: update release notes for hns3 Lijun Ou
2021-01-28  0:25   ` Ferruh Yigit
2021-01-20 13:43 ` [dpdk-dev] [PATCH 3/3] doc: fix hns3 rst Lijun Ou
2021-01-28 12:43 ` [dpdk-dev] [PATCH v2 0/5] update doc for hns3 Lijun Ou
2021-01-28 12:43   ` [dpdk-dev] [PATCH v2 1/5] doc: add FEC in NIC features Lijun Ou
2021-01-28 12:43   ` [dpdk-dev] [PATCH v2 2/5] net/hns3: add FEC feature for hns3.ini Lijun Ou
2021-01-28 14:12     ` Thomas Monjalon
2021-01-29  1:13       ` oulijun
2021-01-29  8:46         ` Ferruh Yigit
2021-01-29  8:57           ` Thomas Monjalon
2021-01-29  9:10           ` oulijun
2021-01-28 12:43   ` [dpdk-dev] [PATCH v2 3/5] net/cxgbe: add FEC feature for cxgbe.ini Lijun Ou
2021-01-28 12:43   ` [dpdk-dev] [PATCH v2 4/5] doc: update release notes for hns3 Lijun Ou
2021-01-28 14:46     ` Ferruh Yigit
2021-01-29  1:28       ` oulijun
2021-01-29  8:48         ` Ferruh Yigit
2021-01-28 12:43   ` [dpdk-dev] [PATCH v2 5/5] doc: fix hns3 rst Lijun Ou
2021-01-29  9:22   ` [dpdk-dev] [PATCH v3 0/3] update doc for hns3 Lijun Ou
2021-01-29  9:22     ` [dpdk-dev] [PATCH v3 1/3] doc: add FEC in NIC features Lijun Ou
2021-01-29  9:22     ` [dpdk-dev] [PATCH v3 2/3] doc: update release notes for hns3 Lijun Ou
2021-01-29  9:22     ` [dpdk-dev] [PATCH v3 3/3] doc: fix hns3 rst Lijun Ou
2021-01-29 11:57     ` [dpdk-dev] [PATCH v3 0/3] update doc for hns3 Ferruh Yigit
2021-02-03  9:43       ` 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=644181ec-5f4c-c2a4-12c5-c5a2428b61e8@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=linuxarm@openeuler.org \
    --cc=oulijun@huawei.com \
    --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).