From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
<netdev@vger.kernel.org>
Cc: <linux-renesas-soc@vger.kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Michal Kubiak <michal.kubiak@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Florian Fainelli <f.fainelli@gmail.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v2 1/2] ravb: avoid PHY being resumed when interface is not up
Date: Thu, 16 Mar 2023 22:56:11 +0300 [thread overview]
Message-ID: <f4f46db5-459a-5479-7fda-7d59517e34a5@omp.ru> (raw)
In-Reply-To: <20230315074115.3008-2-wsa+renesas@sang-engineering.com>
On 3/15/23 10:41 AM, Wolfram Sang wrote:
> RAVB doesn't need mdiobus suspend/resume, that's why it sets
> 'mac_managed_pm'. However, setting it needs to be moved from init to
> probe, so mdiobus PM functions will really never be called (e.g. when
> the interface is not up yet during suspend/resume).
>
> Fixes: 4924c0cdce75 ("net: ravb: Fix PHY state warning splat during system resume")
> Suggested-by: Heiner Kallweit <hkallweit1@gmail.com>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[...]
Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru>
MBR, Sergey
next prev parent reply other threads:[~2023-03-16 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230315074115.3008-1-wsa+renesas@sang-engineering.com>
2023-03-15 7:41 ` Wolfram Sang
2023-03-16 19:56 ` Sergey Shtylyov [this message]
2023-03-16 20:01 ` Florian Fainelli
2023-03-16 20:06 ` Wolfram Sang
2023-03-16 20:07 ` Florian Fainelli
2023-03-15 7:41 ` [PATCH net v2 2/2] sh_eth: " Wolfram Sang
2023-03-16 19:58 ` 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=f4f46db5-459a-5479-7fda-7d59517e34a5@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®