From: Andrew Lunn <andrew@lunn.ch>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com, Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH net-next] Documentation: net: phy: Elaborate on RGMII delay handling
Date: Sun, 16 Feb 2025 17:36:22 +0100 [thread overview]
Message-ID: <92111af4-c0d0-48bd-b774-0cac4f2abd13@lunn.ch> (raw)
In-Reply-To: <20250214114254.0b57693b@fedora.home>
> 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
prev parent reply other threads:[~2025-02-16 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 9:44 [PATCH net-next] Documentation: net: phy: Elaborate on RGMII delay handling Maxime Chevallier
2025-02-14 10:08 ` Russell King (Oracle)
2025-02-14 10:42 ` Maxime Chevallier
2025-02-16 16:36 ` Andrew Lunn [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=92111af4-c0d0-48bd-b774-0cac4f2abd13@lunn.ch \
--to=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox