From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, dev@dpdk.org
Cc: thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH v3 0/2] Support PTP for hns3 PMD
Date: Thu, 1 Apr 2021 17:41:18 +0100 [thread overview]
Message-ID: <43b63b7b-c529-d539-9ca6-8c94f6a9bd4c@intel.com> (raw)
In-Reply-To: <1617284284-27859-1-git-send-email-humin29@huawei.com>
On 4/1/2021 2:38 PM, Min Hu (Connor) wrote:
> This set includes two patches, one patch is to fix
> cyclomatic complexity, the other patch is to support
> PTP, but depends on the first patch. So the two forms
> one set of patches.
> ---
> v3:
> * Delete "RTE_LIBRTE_IEEE1588".
>
> v2:
> * Add release doc for version 21.05.
>
> Min Hu (Connor) (2):
> net/hns3: fix code check warning
> net/hns3: support IEEE 1588 PTP
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-04-01 16:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 8:55 [dpdk-dev] [PATCH " Min Hu (Connor)
2021-03-26 8:56 ` [dpdk-dev] [PATCH 1/2] net/hns3: fix code check warning Min Hu (Connor)
2021-03-26 8:56 ` [dpdk-dev] [PATCH 2/2] net/hns3: support IEEE 1588 PTP Min Hu (Connor)
2021-03-30 13:59 ` Ferruh Yigit
2021-03-31 2:35 ` Min Hu (Connor)
2021-03-31 7:28 ` Thomas Monjalon
2021-03-31 9:26 ` Ferruh Yigit
2021-03-31 11:00 ` Min Hu (Connor)
2021-03-30 14:12 ` Ferruh Yigit
2021-03-31 2:38 ` Min Hu (Connor)
2021-03-31 7:01 ` [dpdk-dev] [PATCH v2 0/2] Support PTP for hns3 PMD Min Hu (Connor)
2021-03-31 7:01 ` [dpdk-dev] [PATCH v2 1/2] net/hns3: fix code check warning Min Hu (Connor)
2021-03-31 7:01 ` [dpdk-dev] [PATCH v2 2/2] net/hns3: support IEEE 1588 PTP Min Hu (Connor)
2021-04-01 13:38 ` [dpdk-dev] [PATCH v3 0/2] Support PTP for hns3 PMD Min Hu (Connor)
2021-04-01 13:38 ` [dpdk-dev] [PATCH v3 1/2] net/hns3: fix code check warning Min Hu (Connor)
2021-04-01 13:38 ` [dpdk-dev] [PATCH v3 2/2] net/hns3: support IEEE 1588 PTP Min Hu (Connor)
2021-04-01 16:41 ` 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=43b63b7b-c529-d539-9ca6-8c94f6a9bd4c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=humin29@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).