[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221109184132.1e0cd0dd@kernel.org>
Date: Wed, 9 Nov 2022 18:41:32 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Aminuddin Jamaluddin <aminuddin.jamaluddin@...el.com>
Cc: Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
Mohammad Athari Bin Ismail <mohammad.athari.ismail@...el.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, tee.min.tan@...el.com,
muhammad.husaini.zulkifli@...el.com, hong.aun.looi@...el.com
Subject: Re: [PATCH net-next v2] net: phy: marvell: add sleep time after
enabling the loopback bit
On Tue, 8 Nov 2022 15:40:05 +0800 Aminuddin Jamaluddin wrote:
> Subject: [PATCH net-next v2] net: phy: marvell: add sleep time after enabling the loopback bit
Looks like v1 was tagged for net, why switch to net-next?
It's either a fix or not, we don't do gray scales in netdev.
> Sleep time is added to ensure the phy to be ready after loopback
> bit was set. This to prevent the phy loopback test from failing.
>
> ---
> V1: https://patchwork.kernel.org/project/netdevbpf/patch/20220825082238.11056-1-aminuddin.jamaluddin@intel.com/
> ---
git am will cut off at the first --- it finds, so the v1 link and all
the tags below we'll be lost when the patch is applied. Please move
this section after the tags.
> Fixes: 020a45aff119 ("net: phy: marvell: add Marvell specific PHY loopback")
> Cc: <stable@...r.kernel.org> # 5.15.x
> Signed-off-by: Muhammad Husaini Zulkifli <muhammad.husaini.zulkifli@...el.com>
> Signed-off-by: Aminuddin Jamaluddin <aminuddin.jamaluddin@...el.com>
Powered by blists - more mailing lists