From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Chris H <christopher.s.hall@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: <david.zage@intel.com>, <vinicius.gomes@intel.com>,
<netdev@vger.kernel.org>, <rodrigo.cadore@l-acoustics.com>,
<vinschen@redhat.com>,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Subject: Re: [PATCH iwl-net v2 1/4] igc: Ensure the PTM cycle is reliably triggered
Date: Tue, 29 Oct 2024 14:21:51 -0700 [thread overview]
Message-ID: <9c396e60-99b3-45be-a147-e1bf6c561183@intel.com> (raw)
In-Reply-To: <20241023023040.111429-2-christopher.s.hall@intel.com>
On 10/22/2024 7:30 PM, Chris H wrote:
...
> static int igc_phc_get_syncdevicetime(ktime_t *device,
> struct system_counterval_t *system,
> void *ctx)
> {
> - u32 stat, t2_curr_h, t2_curr_l, ctrl;
> + u32 stat, t2_curr_h, t2_curr_l;
This needs to move a couple of lines down now for RCT.
Thanks,
Tony
> struct igc_adapter *adapter = ctx;
> struct igc_hw *hw = &adapter->hw;
> int err, count = 100;
next prev parent reply other threads:[~2024-10-29 21:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 2:30 [PATCH iwl-net v2 0/4] igc: Fix PTM timeout Chris H
2024-10-23 2:30 ` [PATCH iwl-net v2 1/4] igc: Ensure the PTM cycle is reliably triggered Chris H
2024-10-29 21:21 ` Tony Nguyen [this message]
2024-10-30 10:17 ` Corinna Vinschen
2024-10-31 9:34 ` [Intel-wired-lan] " Avigail Dahan
2024-10-23 2:30 ` [PATCH iwl-net v2 2/4] igc: Lengthen the hardware retry time to prevent timeouts Chris H
2024-10-31 9:35 ` [Intel-wired-lan] " Avigail Dahan
2024-10-23 2:30 ` [PATCH iwl-net v2 3/4] igc: Move ktime snapshot into PTM retry loop Chris H
2024-10-31 9:35 ` [Intel-wired-lan] " Mor Bar-Gabay
2024-10-23 2:30 ` [PATCH iwl-net v2 4/4] igc: Add lock preventing multiple simultaneous PTM transactions Chris H
2024-10-29 21:20 ` Tony Nguyen
2024-10-30 10:20 ` Corinna Vinschen
2024-10-31 9:36 ` [Intel-wired-lan] " Mor Bar-Gabay
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=9c396e60-99b3-45be-a147-e1bf6c561183@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=christopher.s.hall@intel.com \
--cc=david.zage@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=rodrigo.cadore@l-acoustics.com \
--cc=vinicius.gomes@intel.com \
--cc=vinschen@redhat.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).