Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v2] net: mdiobus: Prevent spike on MDIO bus reset signal
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <161240220718.12107.15347516545043995262.git-patchwork-notify@kernel.org>
Date:   Thu, 04 Feb 2021 01:30:07 +0000
References: <20210202143239.10714-1-mike.looijmans@topic.nl>
In-Reply-To: <20210202143239.10714-1-mike.looijmans@topic.nl>
To:     Mike Looijmans <mike.looijmans@topic.nl>
Cc:     netdev@vger.kernel.org, andrew@lunn.ch, davem@davemloft.net,
        hkallweit1@gmail.com, kuba@kernel.org, linux@armlinux.org.uk,
        linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Tue,  2 Feb 2021 15:32:39 +0100 you wrote:
> The mdio_bus reset code first de-asserted the reset by allocating with
> GPIOD_OUT_LOW, then asserted and de-asserted again. In other words, if
> the reset signal defaulted to asserted, there'd be a short "spike"
> before the reset.
> 
> Here is what happens depending on the pre-existing state of the reset
> signal:
> Reset (previously asserted):   ~~~|_|~~~~|_______
> Reset (previously deasserted): _____|~~~~|_______
>                                   ^ ^    ^
>                                   A B    C
> 
> [...]

Here is the summary with links:
  - [v2] net: mdiobus: Prevent spike on MDIO bus reset signal
    https://git.kernel.org/netdev/net-next/c/e0183b974d30

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html