[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <92111af4-c0d0-48bd-b774-0cac4f2abd13@lunn.ch>
Date: Sun, 16 Feb 2025 17:36:22 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Maxime Chevallier <maxime.chevallier@...tlin.com>
Cc: "Russell King (Oracle)" <linux@...linux.org.uk>, davem@...emloft.net,
netdev@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, thomas.petazzoni@...tlin.com,
Jakub Kicinski <kuba@...nel.org>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Florian Fainelli <f.fainelli@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Simon Horman <horms@...nel.org>, Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH net-next] Documentation: net: phy: Elaborate on RGMII
delay handling
> Just to clarify, do you see that patch as useful ? seems to me like the
> original version is clear enough to you
>
> Thanks for reviewing,
Is the problem that the documentation is confusing? Or that developers
don't actually read the documentation, nor the mailing list?
There is a point of diminishing returns with working on Documentation.
There might be more value in working on checkpatch, add a warning
about any patch adding phy-mode == 'rmgii' without a comment on the
line.
Andrew
Powered by blists - more mailing lists