From: patchwork-bot+netdevbpf@kernel.org
To: Martin Schiller <ms@dev.tdt.de>
Cc: hauke@hauke-m.de, martin.blumenstingl@googlemail.com,
f.fainelli@gmail.com, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] net: phy: intel-xway: enable integrated led functions
Date: Wed, 21 Apr 2021 18:10:09 +0000 [thread overview]
Message-ID: <161902860918.28303.5159266984657312592.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210421055047.22858-1-ms@dev.tdt.de>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Wed, 21 Apr 2021 07:50:47 +0200 you wrote:
> The Intel xway phys offer the possibility to deactivate the integrated
> LED function and to control the LEDs manually.
> If this was set by the bootloader, it must be ensured that the
> integrated LED function is enabled for all LEDs when loading the driver.
>
> Before commit 6e2d85ec0559 ("net: phy: Stop with excessive soft reset")
> the LEDs were enabled by a soft-reset of the PHY (using
> genphy_soft_reset). Initialize the XWAY_MDIO_LED with it's default
> value (which is applied during a soft reset) instead of adding back
> the soft reset. This brings back the default LED configuration while
> still preventing an excessive amount of soft resets.
>
> [...]
Here is the summary with links:
- [net,v3] net: phy: intel-xway: enable integrated led functions
https://git.kernel.org/netdev/net/c/357a07c26697
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:[~2021-04-21 18:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 5:50 [PATCH net v3] net: phy: intel-xway: enable integrated led functions Martin Schiller
2021-04-21 18:10 ` patchwork-bot+netdevbpf [this message]
2021-04-21 21:25 ` Martin Blumenstingl
2022-02-01 20:54 ` Tim Harvey
2022-02-03 1:01 ` Andrew Lunn
2022-02-03 3:12 ` Florian Fainelli
2022-02-03 16:02 ` Tim Harvey
2022-02-04 17:06 ` Florian Fainelli
2022-02-03 15:57 ` Tim Harvey
2022-02-03 16:37 ` Andrew Lunn
2022-02-03 17:52 ` Tim Harvey
2022-02-04 0:04 ` Andrew Lunn
2022-02-04 22:35 ` Tim Harvey
2022-02-04 22:54 ` Andrew Lunn
2022-02-09 16:31 ` Tim Harvey
2022-02-10 0:04 ` Andrew Lunn
2022-02-10 15:52 ` Tim Harvey
2022-02-11 19:17 ` Andrew Lunn
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=161902860918.28303.5159266984657312592.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=martin.blumenstingl@googlemail.com \
--cc=ms@dev.tdt.de \
--cc=netdev@vger.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