From: patchwork-bot+netdevbpf@kernel.org
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org,
netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
robh+dt@kernel.org, andrew@lunn.ch, f.fainelli@gmail.com,
jianxin.pan@amlogic.com, narmstrong@baylibre.com,
khilman@baylibre.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jbrunet@baylibre.com
Subject: Re: [PATCH v4 0/5] dwmac-meson8b: picosecond precision RX delay support
Date: Fri, 08 Jan 2021 00:10:09 +0000 [thread overview]
Message-ID: <161006460922.17100.14707302007622685350.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210106134251.45264-1-martin.blumenstingl@googlemail.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 6 Jan 2021 14:42:46 +0100 you wrote:
> Hello,
>
> with the help of Jianxin Pan (many thanks!) the meaning of the "new"
> PRG_ETH1[19:16] register bits on Amlogic Meson G12A, G12B and SM1 SoCs
> are finally known. These SoCs allow fine-tuning the RGMII RX delay in
> 200ps steps (contrary to what I have thought in the past [0] these are
> not some "calibration" values).
>
> [...]
Here is the summary with links:
- [v4,1/5] dt-bindings: net: dwmac-meson: use picoseconds for the RGMII RX delay
https://git.kernel.org/netdev/net-next/c/6b5903f58df4
- [v4,2/5] net: stmmac: dwmac-meson8b: fix enabling the timing-adjustment clock
https://git.kernel.org/netdev/net-next/c/025822884a4f
- [v4,3/5] net: stmmac: dwmac-meson8b: use picoseconds for the RGMII RX delay
https://git.kernel.org/netdev/net-next/c/140ddf0633df
- [v4,4/5] net: stmmac: dwmac-meson8b: move RGMII delays into a separate function
https://git.kernel.org/netdev/net-next/c/7985244d10ea
- [v4,5/5] net: stmmac: dwmac-meson8b: add support for the RGMII RX delay on G12A
https://git.kernel.org/netdev/net-next/c/de94fc104d58
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-01-08 0:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 13:42 [PATCH v4 0/5] dwmac-meson8b: picosecond precision RX delay support Martin Blumenstingl
2021-01-06 13:42 ` [PATCH v4 1/5] dt-bindings: net: dwmac-meson: use picoseconds for the RGMII RX delay Martin Blumenstingl
2021-01-06 13:42 ` [PATCH v4 2/5] net: stmmac: dwmac-meson8b: fix enabling the timing-adjustment clock Martin Blumenstingl
2021-01-06 13:42 ` [PATCH v4 3/5] net: stmmac: dwmac-meson8b: use picoseconds for the RGMII RX delay Martin Blumenstingl
2021-01-06 13:42 ` [PATCH v4 4/5] net: stmmac: dwmac-meson8b: move RGMII delays into a separate function Martin Blumenstingl
2021-01-06 13:42 ` [PATCH v4 5/5] net: stmmac: dwmac-meson8b: add support for the RGMII RX delay on G12A Martin Blumenstingl
2021-01-08 0:10 ` patchwork-bot+netdevbpf [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=161006460922.17100.14707302007622685350.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=jianxin.pan@amlogic.com \
--cc=khilman@baylibre.com \
--cc=kuba@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.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 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).