public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, woojung.huh@microchip.com,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net v1 1/1] net: lan78xx: fix runtime PM count underflow on link stop
Date: Fri, 01 Mar 2024 08:40:28 +0000	[thread overview]
Message-ID: <170928242803.14717.6883191622320150450.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240228124517.1702476-1-o.rempel@pengutronix.de>

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Wed, 28 Feb 2024 13:45:17 +0100 you wrote:
> Current driver has some asymmetry in the runtime PM calls. On lan78xx_open()
> it will call usb_autopm_get() and unconditionally usb_autopm_put(). And
> on lan78xx_stop() it will call only usb_autopm_put(). So far, it was
> working only because this driver do not activate autosuspend by default,
> so it was visible only by warning "Runtime PM usage count underflow!".
> 
> Since, with current driver, we can't use runtime PM with active link,
> execute lan78xx_open()->usb_autopm_put() only in error case. Otherwise,
> keep ref counting high as long as interface is open.
> 
> [...]

Here is the summary with links:
  - [net,v1,1/1] net: lan78xx: fix runtime PM count underflow on link stop
    https://git.kernel.org/netdev/net/c/1eecc7ab82c4

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



      parent reply	other threads:[~2024-03-01  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 12:45 [PATCH net v1 1/1] net: lan78xx: fix runtime PM count underflow on link stop Oleksij Rempel
2024-02-28 13:18 ` Jiri Pirko
2024-03-01  8:40 ` 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=170928242803.14717.6883191622320150450.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=woojung.huh@microchip.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