From: Florian Fainelli <f.fainelli@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>, Paolo Abeni <pabeni@redhat.com>
Cc: "Jan Petrous (OSS)" <jan.petrous@oss.nxp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net-next v2] net: phy: don't resume device not in use
Date: Tue, 19 Mar 2024 05:31:46 -0700 [thread overview]
Message-ID: <522c63b5-1db0-4e18-9cf3-83bfeadf8c36@gmail.com> (raw)
In-Reply-To: <f6f62bef-5766-4fe1-a6f1-6f18d627737e@lunn.ch>
On 3/19/2024 5:05 AM, Andrew Lunn wrote:
>> Please note that the 'net-next' tree is closed for the merge window.
>> You will have to repost in when the tree will re-open in a week or so.
>>
>> However this change could be suitable for the 'net' tree, if Andrew
>> agrees. If, please re-sent targeting such tree and including a
>> reasonable 'Fixes' tag.
>
> This is the sort of change that i think it should only be in net-next.
> Suspend/resume is complex and not tested too well. There is a chance
> of regression with this change. So we should introduce it slowly.
Totally agree.
--
Florian
next prev parent reply other threads:[~2024-03-19 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 15:45 [RFC PATCH net-next] net: phy: Don't suspend/resume device not in use Jan Petrous (OSS)
2024-03-07 16:22 ` Andrew Lunn
2024-03-07 16:44 ` Jan Petrous (OSS)
2024-03-15 7:55 ` [PATCH net-next v2] net: phy: don't resume " Jan Petrous (OSS)
2024-03-19 11:00 ` Paolo Abeni
2024-03-19 12:05 ` Andrew Lunn
2024-03-19 12:31 ` Florian Fainelli [this message]
2024-03-19 12:02 ` Andrew Lunn
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=522c63b5-1db0-4e18-9cf3-83bfeadf8c36@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=jan.petrous@oss.nxp.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.