From: Jacob Keller <jacob.e.keller@intel.com>
To: Karol Kolacinski <karol.kolacinski@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
anthony.l.nguyen@intel.com, jesse.brandeburg@intel.com
Subject: Re: [Intel-wired-lan] [PATCH iwl-next] ice: remove unnecessary discarding of timestamps
Date: Fri, 27 Oct 2023 11:20:45 -0700 [thread overview]
Message-ID: <418d7ca0-7838-42f3-ad2a-684ea234bdfc@intel.com> (raw)
In-Reply-To: <20231026105955.282546-1-karol.kolacinski@intel.com>
On 10/26/2023 3:59 AM, Karol Kolacinski wrote:
> -/**
> - * ice_ptp_flush_all_tx_tracker - Flush all timestamp trackers on this clock
> - * @pf: Board private structure
> - *
> - * Called by the clock owner to flush all the Tx timestamp trackers associated
> - * with the clock.
> - */
> -static void
> -ice_ptp_flush_all_tx_tracker(struct ice_pf *pf)
> -{
> - struct ice_ptp_port *port;
> -
> - list_for_each_entry(port, &pf->ptp.ports_owner.ports, list_member)
> - ice_ptp_flush_tx_tracker(ptp_port_to_pf(port), &port->tx);
> -}
> -
I think the removal of ice_ptp_flush_all_tx_tracker is likely an
accident possibly due to a merge conflict?
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-10-27 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 10:59 [Intel-wired-lan] [PATCH iwl-next] ice: remove unnecessary discarding of timestamps Karol Kolacinski
2023-10-27 18:19 ` Jacob Keller
2023-10-27 18:20 ` Jacob Keller [this message]
2023-10-27 20:58 ` Jacob Keller
2023-10-30 16:23 ` kernel test robot
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=418d7ca0-7838-42f3-ad2a-684ea234bdfc@intel.com \
--to=jacob.e.keller@intel.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=przemyslaw.kitszel@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