All of lore.kernel.org
 help / color / mirror / Atom feed
From: G, GurucharanX <gurucharanx.g@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH intel-next] ice: Don't put stale timestamps in the skb
Date: Tue, 14 Dec 2021 09:37:10 +0000	[thread overview]
Message-ID: <BYAPR11MB3367FA6D070426952E18543BFC759@BYAPR11MB3367.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211116120714.310539-1-karol.kolacinski@intel.com>



> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of Karol
> Kolacinski
> Sent: Tuesday, November 16, 2021 5:37 PM
> To: intel-wired-lan at lists.osuosl.org
> Cc: Kolacinski, Karol <karol.kolacinski@intel.com>
> Subject: [Intel-wired-lan] [PATCH intel-next] ice: Don't put stale timestamps in
> the skb
> 
> The driver has to check if it does not accidentally put the timestamp in the SKB
> before previous timestamp gets overwritten.
> Timestamp values in the PHY are read only and do not get cleared except at
> hardware reset or when a new timestamp value is captured.
> The cached_tstamp field is used to detect the case where a new timestamp has
> not yet been captured, ensuring that we avoid sending stale timestamp data to
> the stack.
> 
> Signed-off-by: Karol Kolacinski <karol.kolacinski@intel.com>
> ---
>  drivers/net/ethernet/intel/ice/ice_ptp.c | 11 ++++-------
> drivers/net/ethernet/intel/ice/ice_ptp.h |  6 ++++++
>  2 files changed, 10 insertions(+), 7 deletions(-)
> 

Tested-by: Gurucharan G <gurucharanx.g@intel.com> (A Contingent worker at Intel)

  reply	other threads:[~2021-12-14  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 12:07 [Intel-wired-lan] [PATCH intel-next] ice: Don't put stale timestamps in the skb Karol Kolacinski
2021-12-14  9:37 ` G, GurucharanX [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-12 13:53 Karol Kolacinski
2021-11-13  1:09 ` Jesse Brandeburg
2021-11-04 13:58 Karol Kolacinski

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=BYAPR11MB3367FA6D070426952E18543BFC759@BYAPR11MB3367.namprd11.prod.outlook.com \
    --to=gurucharanx.g@intel.com \
    --cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.