From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 1/2] igc: Fix wrong timestamp latency numbers
Date: Tue, 18 Aug 2020 15:52:31 -0700 [thread overview]
Message-ID: <87h7szr2hc.fsf@intel.com> (raw)
In-Reply-To: <20200818143615.00000f16@intel.com>
Jesse Brandeburg <jesse.brandeburg@intel.com> writes:
> Vinicius Costa Gomes wrote:
>
>> The previous timestamping latency numbers were obtained by
>> interpolating the i210 numbers with the i225 crystal clock value. That
>> calculation was wrong.
>>
>> Use the correct values from real measurements.
>>
>> Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
>
> Is this targeted at net or net-next, and because it is a fix I
> recommend you have subject
> [PATCH net 1/2]
Oh, sorry about that. I used the wrong 'git format-patch' line.
>
> and you should include a "Fixes:" tag since this driver has been
> released in previous kernels.
Yes. This should have been directed to 'net-queue', thanks for noticing.
Will send a v2.
Cheers,
--
Vinicius
next prev parent reply other threads:[~2020-08-18 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 23:12 [Intel-wired-lan] [PATCH 1/2] igc: Fix wrong timestamp latency numbers Vinicius Costa Gomes
2020-08-17 23:12 ` [Intel-wired-lan] [PATCH 2/2] igc: Fix not considering the TX delay for timestamps Vinicius Costa Gomes
2020-08-18 21:37 ` Jesse Brandeburg
2020-08-26 22:02 ` Brown, Aaron F
2020-08-18 21:36 ` [Intel-wired-lan] [PATCH 1/2] igc: Fix wrong timestamp latency numbers Jesse Brandeburg
2020-08-18 22:52 ` Vinicius Costa Gomes [this message]
2020-08-26 22:02 ` Brown, Aaron F
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=87h7szr2hc.fsf@intel.com \
--to=vinicius.gomes@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.