[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231120135303.0e64bc81@kernel.org>
Date: Mon, 20 Nov 2023 13:53:03 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Christian Marangi <ansuelsmth@...il.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>,
Florian Fainelli <f.fainelli@...il.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [net-next PATCH] net: phy: correctly check soft_reset ret ONLY
if defined for PHY
On Mon, 20 Nov 2023 17:50:53 +0100 Christian Marangi wrote:
> On Mon, Nov 20, 2023 at 09:42:34AM -0800, Jakub Kicinski wrote:
> > On Mon, 20 Nov 2023 14:15:40 +0100 Christian Marangi wrote:
> > > Luckly nothing was ever added before the soft_reset call so the ret
> > > check (in the case where a PHY didn't had soft_reset defined) although
> > > wrong, never caused problems as ret was init 0 at the start of
> > > phy_init_hw.
> >
> > not currently a bug => no Fixes tag, please
>
> I know it's not a bug but still the referenced commit was wrong. Can I
> at least use Ref to reference it?
Not sure what you mean by "Ref"
> Due to the changes done to this function, it's hard to catch where the
> problem arised with a git blame.
Right, and you already quote the commit in the body. No objections to
repeating that if you want, maybe:
Introduced by commit 6e2d85ec0559 ("net: phy: Stop with excessive soft
reset").
but as a part of the "body" of the commit message, not tags.
Powered by blists - more mailing lists