From: Simei Su <simei.su@intel.com>
To: qi.z.zhang@intel.com, junfeng.guo@intel.com
Cc: dev@dpdk.org, wenjun1.wu@intel.com, Simei Su <simei.su@intel.com>
Subject: [PATCH v2 0/3] net/igc: support PTP timesync
Date: Tue, 17 Jan 2023 21:26:16 +0800 [thread overview]
Message-ID: <20230117132619.83712-1-simei.su@intel.com> (raw)
In-Reply-To: <20221220034103.441524-1-simei.su@intel.com>
[PATCH v2 1/3] code refactoring.
[PATCH v2 2/3] add related definitions for ptp timesync.
[PATCH v2 3/3] add IEEE1588 API to support timesync.
v2:
* Refine commit log.
* Update the doc/guides/nics/features/igc.ini to add "Timesync" feature.
* Add release notes.
Simei Su (3):
net/igc: code refactoring
net/igc/base: support PTP timesync
net/igc: support IEEE 1588 PTP
doc/guides/nics/features/igc.ini | 1 +
doc/guides/rel_notes/release_23_03.rst | 3 +
drivers/net/igc/base/igc_defines.h | 11 ++
drivers/net/igc/igc_ethdev.c | 222 +++++++++++++++++++++++++++++++++
drivers/net/igc/igc_ethdev.h | 4 +-
drivers/net/igc/igc_txrx.c | 166 +++++++-----------------
drivers/net/igc/igc_txrx.h | 116 +++++++++++++++++
7 files changed, 401 insertions(+), 122 deletions(-)
--
2.9.5
next prev parent reply other threads:[~2023-01-17 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 3:41 [PATCH " Simei Su
2022-12-20 3:41 ` [PATCH 1/3] net/igc: code refactoring Simei Su
2023-01-17 2:25 ` Zhang, Qi Z
2023-01-17 4:00 ` Su, Simei
2022-12-20 3:41 ` [PATCH 2/3] net/igc/base: support PTP timesync Simei Su
2022-12-20 3:41 ` [PATCH 3/3] net/igc: support IEEE 1588 PTP Simei Su
2023-01-17 13:26 ` Simei Su [this message]
2023-01-17 13:26 ` [PATCH v2 1/3] net/igc: code refactoring Simei Su
2023-01-17 13:26 ` [PATCH v2 2/3] net/igc/base: support PTP timesync Simei Su
2023-01-17 13:26 ` [PATCH v2 3/3] net/igc: support IEEE 1588 PTP Simei Su
2023-01-29 13:05 ` [PATCH v2 0/3] net/igc: support PTP timesync Zhang, Qi Z
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=20230117132619.83712-1-simei.su@intel.com \
--to=simei.su@intel.com \
--cc=dev@dpdk.org \
--cc=junfeng.guo@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=wenjun1.wu@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).