From: Brett Creeley <bcreeley@amd.com>
To: Karol Kolacinski <karol.kolacinski@intel.com>,
intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, anthony.l.nguyen@intel.com,
jesse.brandeburg@intel.com
Subject: Re: [Intel-wired-lan] [PATCH v4 iwl-next 0/6] ice: fix timestamping in reset process
Date: Thu, 21 Dec 2023 10:20:06 -0800 [thread overview]
Message-ID: <050f2151-6dd3-269e-dddc-941d6d343d76@amd.com> (raw)
In-Reply-To: <20231221100326.1030761-1-karol.kolacinski@intel.com>
On 12/21/2023 2:03 AM, Karol Kolacinski wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> PTP reset process has multiple places where timestamping can end up in
> an incorrect state.
>
> This series introduces a proper state machine for PTP and refactors
> a large part of the code to ensure that timestamping does not break.
>
>
> Jacob Keller (5):
> ice: pass reset type to PTP reset functions
> ice: rename verify_cached to has_ready_bitmap
> ice: rename ice_ptp_tx_cfg_intr
> ice: factor out ice_ptp_rebuild_owner()
> ice: stop destroying and reinitalizing Tx tracker during reset
>
> Karol Kolacinski (1):
> ice: introduce PTP state machine
>
> V2 -> V3: rebased the series fixed Tx timestamps missing
> V1 -> V2: rebased the series and dropped already merged patches
>
> drivers/net/ethernet/intel/ice/ice.h | 1 -
> drivers/net/ethernet/intel/ice/ice_ethtool.c | 2 +-
> drivers/net/ethernet/intel/ice/ice_main.c | 4 +-
> drivers/net/ethernet/intel/ice/ice_ptp.c | 231 +++++++++++--------
> drivers/net/ethernet/intel/ice/ice_ptp.h | 34 ++-
> 5 files changed, 166 insertions(+), 106 deletions(-)
For the series:
Reviewed-by: Brett Creeley <brett.creeley@amd.com>
>
>
> base-commit: 67b40ee196fd2fd6d9b7f9b58912587c837bdc39
> --
> 2.40.1
>
>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2023-12-21 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 10:03 [Intel-wired-lan] [PATCH v4 iwl-next 0/6] ice: fix timestamping in reset process Karol Kolacinski
2023-12-21 10:03 ` [Intel-wired-lan] [PATCH v4 iwl-next 1/6] ice: introduce PTP state machine Karol Kolacinski
2023-12-21 10:03 ` [Intel-wired-lan] [PATCH v4 iwl-next 2/6] ice: pass reset type to PTP reset functions Karol Kolacinski
2023-12-23 18:22 ` Simon Horman
2023-12-21 10:03 ` [Intel-wired-lan] [PATCH v4 iwl-next 3/6] ice: rename verify_cached to has_ready_bitmap Karol Kolacinski
2023-12-21 10:03 ` [Intel-wired-lan] [PATCH v4 iwl-next 4/6] ice: rename ice_ptp_tx_cfg_intr Karol Kolacinski
2023-12-21 10:03 ` [Intel-wired-lan] [PATCH v4 iwl-next 5/6] ice: factor out ice_ptp_rebuild_owner() Karol Kolacinski
2023-12-21 10:20 ` Sokolowski, Jan
2023-12-21 23:54 ` Keller, Jacob E
2023-12-21 10:03 ` [Intel-wired-lan] [PATCH v4 iwl-next 6/6] ice: stop destroying and reinitalizing Tx tracker during reset Karol Kolacinski
2023-12-21 18:20 ` Brett Creeley [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=050f2151-6dd3-269e-dddc-941d6d343d76@amd.com \
--to=bcreeley@amd.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=karol.kolacinski@intel.com \
--cc=netdev@vger.kernel.org \
/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