From: patchwork-bot+netdevbpf@kernel•org
To: Geert Uytterhoeven <geert+renesas@glider•be>
Cc: s.shtylyov@omp•ru, davem@davemloft•net, kuba@kernel•org,
yoshihiro.shimoda.uh@renesas•com, netdev@vger•kernel.org,
linux-renesas-soc@vger•kernel.org
Subject: Re: [PATCH net-next] ravb: Remove checks for unsupported internal delay modes
Date: Fri, 13 Aug 2021 23:20:06 +0000 [thread overview]
Message-ID: <162889680666.8729.6362809405452590677.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <2037542ac56e99413b9807e24049711553cc88a9.1628696778.git.geert+renesas@glider.be>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 11 Aug 2021 17:49:00 +0200 you wrote:
> The EtherAVB instances on the R-Car E3/D3 and RZ/G2E SoCs do not support
> TX clock internal delay modes, and the EtherAVB driver prints a warning
> if an unsupported "rgmii-*id" PHY mode is specified, to catch buggy
> DTBs.
>
> Commit a6f51f2efa742df0 ("ravb: Add support for explicit internal
> clock delay configuration") deprecated deriving the internal delay mode
> from the PHY mode, in favor of explicit configuration using the now
> mandatory "rx-internal-delay-ps" and "tx-internal-delay-ps" properties,
> thus delegating the warning to the legacy fallback code.
>
> [...]
Here is the summary with links:
- [net-next] ravb: Remove checks for unsupported internal delay modes
https://git.kernel.org/netdev/net-next/c/44e5d0881280
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-08-13 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 15:49 [PATCH net-next] ravb: Remove checks for unsupported internal delay modes Geert Uytterhoeven
2021-08-12 9:30 ` Niklas Söderlund
2021-08-13 23:20 ` 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=162889680666.8729.6362809405452590677.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=geert+renesas@glider$(echo .)be \
--cc=kuba@kernel$(echo .)org \
--cc=linux-renesas-soc@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=s.shtylyov@omp$(echo .)ru \
--cc=yoshihiro.shimoda.uh@renesas$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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