From: Jacob Keller <jacob.e.keller@intel.com>
To: Alison Chaiken <achaiken@aurora.tech>, <anthony.l.nguyen@intel.com>
Cc: Steve Payne <spayne@aurora.tech>,
netdev@vger.kernel.org, richardcochran@gmail.com,
intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] Fwd: [PATCH] Use ixgbe_ptp_reset on linkup/linkdown for X550
Date: Tue, 4 Oct 2022 14:08:22 -0700 [thread overview]
Message-ID: <e4139591-0773-0e82-efc8-2afd2a0813d8@intel.com> (raw)
In-Reply-To: <CAFzL-7v-wLuaunUwKfEy0W+OMkKSXJ8ohecb8_Gok+=eQHdeAA@mail.gmail.com>
On 10/4/2022 11:14 AM, Alison Chaiken wrote:
> How about this Intel X550 PTP fix for 6.1?
>
> https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20220801/029590.html
>
> Thanks,
> Alison Chaiken
> Aurora Innovation
>
This was already submitted to net as [1], and it looks like it's already
applied to the stable Linux 5.19, 5.15, and 5.10 stable trees.
I've confirmed that it's in the v6.0 tag as commit 25d7a5f5a6bb ("ixgbe:
stop resetting SYSTIME in ixgbe_ptp_start_cyclecounter")
[1]
https://lore.kernel.org/netdev/20220824193748.874343-2-anthony.l.nguyen@intel.com/
Hope that helps!
Thanks,
Jake
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2022-10-04 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 13:37 [Intel-wired-lan] [PATCH] Use ixgbe_ptp_reset on linkup/linkdown for X550 achaiken
2022-08-01 21:34 ` Keller, Jacob E
[not found] ` <CAFzL-7tX845o2kJmE4o8EhbeD-=vkR6rmaiz_ZEWfSD4W+iWEA@mail.gmail.com>
2022-08-01 22:53 ` Ilya Evenbach
2022-08-01 23:00 ` [Intel-wired-lan] Fwd: " Ilya Evenbach
2022-08-01 23:29 ` Jacob Keller
2022-08-02 0:24 ` Alison Chaiken
2022-08-02 0:38 ` Jacob Keller
2022-08-02 0:26 ` Jacob Keller
2022-10-04 18:14 ` Alison Chaiken
2022-10-04 21:08 ` Jacob Keller [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=e4139591-0773-0e82-efc8-2afd2a0813d8@intel.com \
--to=jacob.e.keller@intel.com \
--cc=achaiken@aurora.tech \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=spayne@aurora.tech \
/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