From: patchwork-bot+netdevbpf@kernel.org
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, p.zabel@pengutronix.de, s.shtylyov@omp.ru,
geert+renesas@glider.be, liuhangbin@gmail.com,
mitsuhiro.kimura.kc@renesas.com, netdev@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
fabrizio.castro.jz@renesas.com, stable@vger.kernel.org,
leonro@nvidia.com
Subject: Re: [PATCH net v2] ravb: Fix "failed to switch device to config mode" message during unbind
Date: Thu, 15 Dec 2022 14:40:16 +0000 [thread overview]
Message-ID: <167111521604.32410.3850134562584373463.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221214105118.2495313-1-biju.das.jz@bp.renesas.com>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 14 Dec 2022 10:51:18 +0000 you wrote:
> This patch fixes the error "ravb 11c20000.ethernet eth0: failed to switch
> device to config mode" during unbind.
>
> We are doing register access after pm_runtime_put_sync().
>
> We usually do cleanup in reverse order of init. Currently in
> remove(), the "pm_runtime_put_sync" is not in reverse order.
>
> [...]
Here is the summary with links:
- [net,v2] ravb: Fix "failed to switch device to config mode" message during unbind
https://git.kernel.org/netdev/net/c/c72a7e42592b
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:[~2022-12-15 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 10:51 [PATCH net v2] ravb: Fix "failed to switch device to config mode" message during unbind Biju Das
2022-12-15 14:40 ` patchwork-bot+netdevbpf [this message]
2022-12-15 16:43 ` Sergey Shtylyov
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=167111521604.32410.3850134562584373463.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=mitsuhiro.kimura.kc@renesas.com \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=s.shtylyov@omp.ru \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.