[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230112213034.074ff77e@kernel.org>
Date: Thu, 12 Jan 2023 21:30:34 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Xu Liang <lxu@...linear.com>
Cc: <andrew@...n.ch>, <hkallweit1@...il.com>, <netdev@...r.kernel.org>,
<davem@...emloft.net>, <linux@...linux.org.uk>,
<hmehrtens@...linear.com>, <tmohren@...linear.com>,
<mohammad.athari.ismail@...el.com>, <edumazet@...gle.com>,
<michael@...le.cc>, <pabeni@...hat.com>
Subject: Re: [PATCH net-next v3] net: phy: mxl-gpy: fix delay time required
by loopback disable function
On Wed, 11 Jan 2023 16:22:01 +0800 Xu Liang wrote:
> GPY2xx devices need 3 seconds to fully switch out of loopback mode
> before it can safely re-enter loopback mode.
>
> Signed-off-by: Xu Liang <lxu@...linear.com>
Looks like a fix, it needs a Fixes tag and needs to go to net.
Michael already asked you for the Fixes tag on v2, why did you decide
to switch to net-next instead?
We don't route fixes to net-next when they are targeting less
important features, in case that's your reason. Either something
is a fix or it's not. If you think this is not a fix - you need to
explain in the commit message why.
Powered by blists - more mailing lists