From: patchwork-bot+netdevbpf@kernel.org
To: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@ew.tq-group.com
Subject: Re: [PATCH net-next v2 1/2] net: phy: dp83867: remove check of delay strap configuration
Date: Tue, 13 May 2025 01:50:40 +0000 [thread overview]
Message-ID: <174710104099.1140764.3443141386410446022.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <8a286207cd11b460bb0dbd27931de3626b9d7575.1746612711.git.matthias.schiffer@ew.tq-group.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 7 May 2025 12:13:20 +0200 you wrote:
> The check that intended to handle "rgmii" PHY mode differently to the
> RGMII modes with internal delay never worked as intended:
>
> - added in commit 2a10154abcb7 ("net: phy: dp83867: Add TI dp83867 phy"):
> logic error caused the condition to always evaluate to true
> - changed in commit a46fa260f6f5 ("net: phy: dp83867: Fix warning check
> for setting the internal delay"): now the condition incorrectly
> evaluates to false for rgmii-txid
> - removed in commit 2b892649254f ("net: phy: dp83867: Set up RGMII TX
> delay")
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: phy: dp83867: remove check of delay strap configuration
https://git.kernel.org/netdev/net-next/c/cc7734e03e81
- [net-next,v2,2/2] net: phy: dp83867: use 2ns delay if not specified in DTB
https://git.kernel.org/netdev/net-next/c/6bf78849371d
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:[~2025-05-13 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 10:13 Matthias Schiffer
2025-05-07 10:13 ` [PATCH net-next v2 2/2] net: phy: dp83867: use 2ns delay if not specified in DTB Matthias Schiffer
2025-05-13 1:50 ` 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=174710104099.1140764.3443141386410446022.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@ew.tq-group.com \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®