From: Simon Horman <simon.horman@corigine•com>
To: Wolfram Sang <wsa+renesas@sang-engineering•com>
Cc: netdev@vger•kernel.org, linux-renesas-soc@vger•kernel.org,
Geert Uytterhoeven <geert+renesas@glider•be>,
Steve Glendinning <steve.glendinning@shawell•net>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH net v2 1/2] smsc911x: only update stats when interface is up
Date: Mon, 20 Mar 2023 17:32:56 +0100 [thread overview]
Message-ID: <ZBiKuJZdpGHXGImm@corigine.com> (raw)
In-Reply-To: <20230320092041.1656-2-wsa+renesas@sang-engineering.com>
On Mon, Mar 20, 2023 at 10:20:40AM +0100, Wolfram Sang wrote:
> Otherwise the clocks are not enabled and reading registers will BUG.
>
> Fixes: 1e30b8d755b8 ("net: smsc911x: Make Runtime PM handling more fine-grained")
> Suggested-by: Geert Uytterhoeven <geert+renesas@glider•be>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering•com>
Reviewed-by: Simon Horman <simon.horman@corigine•com>
next prev parent reply other threads:[~2023-03-20 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 9:20 [PATCH net v2 0/2] smsc911x: fix issues when interface is not up yet Wolfram Sang
2023-03-20 9:20 ` [PATCH net v2 1/2] smsc911x: only update stats when interface is up Wolfram Sang
2023-03-20 16:32 ` Simon Horman [this message]
2023-03-21 16:59 ` Florian Fainelli
2023-03-20 9:20 ` [PATCH net v2 2/2] smsc911x: avoid PHY being resumed when interface is not up Wolfram Sang
2023-03-20 16:33 ` Simon Horman
2023-03-21 14:39 ` Paolo Abeni
2023-03-21 17:56 ` Wolfram Sang
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=ZBiKuJZdpGHXGImm@corigine.com \
--to=simon.horman@corigine$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=geert+renesas@glider$(echo .)be \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-renesas-soc@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=steve.glendinning@shawell$(echo .)net \
--cc=wsa+renesas@sang-engineering$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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