From: patchwork-bot+netdevbpf@kernel.org
To: Dimitri Fedrau via B4 Relay
<devnull+dimitri.fedrau.liebherr.com@kernel.org>
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, dima.fedrau@gmail.com,
gerhard@engleder-embedded.com, dimitri.fedrau@liebherr.com
Subject: Re: [PATCH v2] net: phy: dp83822: fix transmit amplitude if CONFIG_OF_MDIO not defined
Date: Mon, 24 Mar 2025 17:00:34 +0000 [thread overview]
Message-ID: <174283563452.4097226.5621496775450844248.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250317-dp83822-fix-transceiver-mdio-v2-1-fb09454099a4@liebherr.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 17 Mar 2025 08:48:34 +0100 you wrote:
> From: Dimitri Fedrau <dimitri.fedrau@liebherr.com>
>
> When CONFIG_OF_MDIO is not defined the index for selecting the transmit
> amplitude voltage for 100BASE-TX is set to 0, but it should be -1, if there
> is no need to modify the transmit amplitude voltage. Move initialization of
> the index from dp83822_of_init to dp8382x_probe.
>
> [...]
Here is the summary with links:
- [v2] net: phy: dp83822: fix transmit amplitude if CONFIG_OF_MDIO not defined
https://git.kernel.org/netdev/net-next/c/8fa649fd7d30
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-03-24 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 7:48 [PATCH v2] net: phy: dp83822: fix transmit amplitude if CONFIG_OF_MDIO not defined Dimitri Fedrau via B4 Relay
2025-03-24 17:00 ` 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=174283563452.4097226.5621496775450844248.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devnull+dimitri.fedrau.liebherr.com@kernel.org \
--cc=dima.fedrau@gmail.com \
--cc=dimitri.fedrau@liebherr.com \
--cc=edumazet@google.com \
--cc=gerhard@engleder-embedded.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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