From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>,
netdev@vger.kernel.org, lxu@maxlinear.com, hkallweit1@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-kernel@vger.kernel.org,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next] net: phy: add wol config options in phy device
Date: Tue, 7 May 2024 09:25:03 +0100 [thread overview]
Message-ID: <ZjnlX9/lm6OK39zl@shell.armlinux.org.uk> (raw)
In-Reply-To: <4a565d54-f468-4e32-8a2c-102c1203f72c@lunn.ch>
On Mon, May 06, 2024 at 03:28:33AM +0200, Andrew Lunn wrote:
> You should first answer Russell question. It could be a totally
> different scheme might come of of the discussion with Russell.
Yes please. We definitely need to get to the bottom of what is going
on here _before_ we come up with a solution.
If we don't understand the problem, whatever fix gets proposed is
probably going to be nothing more than a bodge job - and then someone
else is going to have a problem and propose another bodge job and so
we'll end up with bodge job on top of more bodge jobs.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2024-05-07 8:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 5:06 [PATCH net-next] net: phy: add wol config options in phy device Raju Lakkaraju
2024-05-02 13:49 ` Paolo Abeni
2024-05-03 9:22 ` Raju Lakkaraju
2024-05-02 14:51 ` Andrew Lunn
2024-05-02 15:59 ` Russell King (Oracle)
2024-05-02 16:17 ` Florian Fainelli
2024-05-02 16:37 ` Andrew Lunn
2024-05-07 10:20 ` Raju Lakkaraju
2024-05-07 11:53 ` Russell King (Oracle)
2024-05-07 16:18 ` Ronnie.Kunin
2024-05-07 17:56 ` Russell King (Oracle)
2024-05-07 18:58 ` Ronnie.Kunin
2024-05-03 9:37 ` Raju Lakkaraju
2024-05-06 1:28 ` Andrew Lunn
2024-05-07 8:25 ` Russell King (Oracle) [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=ZjnlX9/lm6OK39zl@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Raju.Lakkaraju@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lxu@maxlinear.com \
--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.