From: patchwork-bot+netdevbpf@kernel.org
To: Zong Li <zong.li@sifive.com>
Cc: nicolas.ferre@microchip.com, claudiu.beznea@microchip.com,
davem@davemloft.net, kuba@kernel.org, f.fainelli@gmail.com,
palmer@dabbelt.com, paul.walmsley@sifive.com,
schwab@linux-m68k.org, sboyd@kernel.org, aou@eecs.berkeley.edu,
mturquette@baylibre.com, geert@linux-m68k.org,
yixun.lan@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2] net: macb: ensure the device is available before accessing GEMGXL control registers
Date: Sun, 23 May 2021 23:20:10 +0000 [thread overview]
Message-ID: <162181201014.2631.11068199845594648051.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210522091611.36920-1-zong.li@sifive.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Sat, 22 May 2021 17:16:11 +0800 you wrote:
> If runtime power menagement is enabled, the gigabit ethernet PLL would
> be disabled after macb_probe(). During this period of time, the system
> would hang up if we try to access GEMGXL control registers.
>
> We can't put runtime_pm_get/runtime_pm_put/ there due to the issue of
> sleep inside atomic section (7fa2955ff70ce453 ("sh_eth: Fix sleeping
> function called from invalid context"). Add netif_running checking to
> ensure the device is available before accessing GEMGXL device.
>
> [...]
Here is the summary with links:
- [v2] net: macb: ensure the device is available before accessing GEMGXL control registers
https://git.kernel.org/netdev/net/c/5eff1461a6de
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-05-23 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 9:16 [PATCH v2] net: macb: ensure the device is available before accessing GEMGXL control registers Zong Li
2021-05-23 23:20 ` 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=162181201014.2631.11068199845594648051.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=geert@linux-m68k.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=sboyd@kernel.org \
--cc=schwab@linux-m68k.org \
--cc=yixun.lan@gmail.com \
--cc=zong.li@sifive.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;
as well as URLs for NNTP newsgroup(s).