From: Miroslav Lichvar <mlichvar@redhat.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: Matt Corallo <ntp-lists@mattcorallo.com>,
intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH net-next] igb: Fix PPS input and output using 3rd and 4th SDP
Date: Thu, 2 Feb 2023 18:34:14 +0100 [thread overview]
Message-ID: <Y9v0Fvek9Hc4i+4C@localhost> (raw)
In-Reply-To: <7654b674-1589-8e1f-338e-4556dc716f48@intel.com>
On Thu, Feb 02, 2023 at 09:10:57AM -0800, Tony Nguyen wrote:
> On 2/1/2023 6:36 AM, Miroslav Lichvar wrote:
> > Fix handling of the tsync interrupt to compare the pin number with
> > IGB_N_SDP instead of IGB_N_EXTTS/IGB_N_PEROUT and fix the indexing to
> > the perout array.
> >
> > Fixes: cf99c1dd7b77 ("igb: move PEROUT and EXTTS isr logic to separate functions")
> > Reported-by: Matt Corallo <ntp-lists@mattcorallo.com>
>
> This is marked for net-next but with the fixes and reported-by, should this
> be net?
I wasn't sure with net as the PPS output feature wasn't tested yet and
it touched new code added for I350 since the buggy commit. If that's
ok, make it net.
Thanks,
--
Miroslav Lichvar
_______________________________________________
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-02-02 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 14:36 [Intel-wired-lan] [PATCH net-next] igb: Fix PPS input and output using 3rd and 4th SDP Miroslav Lichvar
2023-02-02 0:25 ` Jacob Keller
2023-02-02 17:10 ` Tony Nguyen
2023-02-02 17:34 ` Matt Corallo
2023-02-02 17:34 ` Miroslav Lichvar [this message]
2023-02-13 4:03 ` G, GurucharanX
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=Y9v0Fvek9Hc4i+4C@localhost \
--to=mlichvar@redhat.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ntp-lists@mattcorallo.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