From: patchwork-bot+netdevbpf@kernel.org
To: Johannes Zink <j.zink@pengutronix.de>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
richardcochran@gmail.com, linux@armlinux.org.uk,
patchwork-jzi@pengutronix.de, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
lkp@intel.com
Subject: Re: [PATCH v2] net: stmmac: correct MAC propagation delay
Date: Wed, 26 Jul 2023 03:50:19 +0000 [thread overview]
Message-ID: <169034341942.4604.1855470719545245647.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230719-stmmac_correct_mac_delay-v2-1-3366f38ee9a6@pengutronix.de>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 24 Jul 2023 12:01:31 +0200 you wrote:
> The IEEE1588 Standard specifies that the timestamps of Packets must be
> captured when the PTP message timestamp point (leading edge of first
> octet after the start of frame delimiter) crosses the boundary between
> the node and the network. As the MAC latches the timestamp at an
> internal point, the captured timestamp must be corrected for the
> additional path latency, as described in the publicly available
> datasheet [1].
>
> [...]
Here is the summary with links:
- [v2] net: stmmac: correct MAC propagation delay
https://git.kernel.org/netdev/net-next/c/20bf98c94146
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-07-26 3:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 10:01 [PATCH v2] net: stmmac: correct MAC propagation delay Johannes Zink
2023-07-26 3:06 ` Jakub Kicinski
2023-07-26 3:22 ` Richard Cochran
2023-07-26 3:39 ` Jakub Kicinski
2023-07-26 6:04 ` Marc Kleine-Budde
2023-07-26 15:34 ` Richard Cochran
2023-07-27 6:40 ` Johannes Zink
2023-07-27 6:40 ` Johannes Zink
2023-07-27 13:30 ` Richard Cochran
2023-07-27 13:30 ` Richard Cochran
2023-07-26 6:10 ` Johannes Zink
2023-07-26 15:43 ` Richard Cochran
2023-07-27 6:39 ` Johannes Zink
2023-07-27 6:39 ` Johannes Zink
2023-07-27 6:55 ` Johannes Zink
2023-07-27 6:55 ` Johannes Zink
2023-07-27 7:41 ` Johannes Zink
2023-07-27 7:41 ` Johannes Zink
2023-07-27 7:15 ` Kurt Kanzenbach
2023-07-27 7:15 ` Kurt Kanzenbach
2023-07-27 7:18 ` Johannes Zink
2023-07-27 7:18 ` Johannes Zink
2023-07-26 5:50 ` Marc Kleine-Budde
2023-07-26 3:50 ` patchwork-bot+netdevbpf [this message]
2023-07-26 18:00 ` Richard Cochran
2023-07-27 6:42 ` Johannes Zink
2023-07-27 6:42 ` Johannes Zink
2023-07-27 13:34 ` Richard Cochran
2023-07-27 13:34 ` Richard Cochran
2023-07-26 20:57 ` Richard Cochran
2023-07-27 7:20 ` Johannes Zink
2023-07-27 7:20 ` Johannes Zink
2023-07-27 13:36 ` Richard Cochran
2023-07-27 13:36 ` Richard Cochran
2023-07-31 7:00 ` Johannes Zink
2023-07-31 7:00 ` Johannes Zink
2023-07-31 13:44 ` Richard Cochran
2023-07-31 13:44 ` Richard Cochran
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=169034341942.4604.1855470719545245647.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.zink@pengutronix.de \
--cc=joabreu@synopsys.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-jzi@pengutronix.de \
--cc=peppe.cavallaro@st.com \
--cc=richardcochran@gmail.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 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.