public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Paul Cercueil <paul@crapouillou.net>
Cc: davem@davemloft.net, kuba@kernel.org, od@zcrc.me,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] net: davicom: Fix regulator not turned off on failed probe
Date: Mon, 08 Mar 2021 20:10:08 +0000	[thread overview]
Message-ID: <161523420843.27243.17192886779484123674.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210307131749.14960-1-paul@crapouillou.net>

Hello:

This series was applied to netdev/net.git (refs/heads/master):

On Sun,  7 Mar 2021 13:17:47 +0000 you wrote:
> When the probe fails or requests to be defered, we must disable the
> regulator that was previously enabled.
> 
> Fixes: 7994fe55a4a2 ("dm9000: Add regulator and reset support to dm9000")
> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> ---
>  drivers/net/ethernet/davicom/dm9000.c | 12 +++++++++---
>  1 file changed, 9 insertions(+), 3 deletions(-)

Here is the summary with links:
  - [1/3] net: davicom: Fix regulator not turned off on failed probe
    https://git.kernel.org/netdev/net/c/ac88c531a5b3
  - [2/3] net: davicom: Fix regulator not turned off on driver removal
    https://git.kernel.org/netdev/net/c/cf9e60aa69ae
  - [3/3] net: davicom: Use platform_get_irq_optional()
    https://git.kernel.org/netdev/net/c/2e2696223676

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



      parent reply	other threads:[~2021-03-08 20:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07 13:17 [PATCH 1/3] net: davicom: Fix regulator not turned off on failed probe Paul Cercueil
2021-03-07 13:17 ` [PATCH 2/3] net: davicom: Fix regulator not turned off on driver removal Paul Cercueil
2021-03-07 13:17 ` [PATCH 3/3] net: davicom: Use platform_get_irq_optional() Paul Cercueil
2021-03-08 20:10 ` 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=161523420843.27243.17192886779484123674.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=od@zcrc.me \
    --cc=paul@crapouillou.net \
    /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