From: Jonathan Corbet <corbet@lwn.net>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v1 1/1] net: phy: Move callback comments from struct to kernel-doc section
Date: Thu, 02 Jan 2025 11:01:54 -0700 [thread overview]
Message-ID: <87seq1xffx.fsf@trenco.lwn.net> (raw)
In-Reply-To: <Z3bFWDjtGNqSGfdD@shell.armlinux.org.uk>
"Russell King (Oracle)" <linux@armlinux.org.uk> writes:
> This is the fundamental problem with kernel-doc, when it's missing
> something that really should already be there. It's not like we're
> the first to use function pointers in structs - that's a thing that
> the kernel has been doing for decades.
Unfortunately, kernel-doc is a gnarly collection of Perl regexes that
first appeared in 2.3.52pre1 some 25 years ago and has only grown more
gnarly since.
> I also have no desire to attempt to fix kernel-doc -
Neither does anybody else. There are a few of us who will mount an
expedition into those dark woods on occasion to fix something, but there
is little desire on any part to make significant improvements, including
adding things that should already be there. It's just barely
maintainable.
The proper solution is to reimplement kernel-doc in a language that
people actually want to deal with, cleaning out 25 years of cruft in the
process. One way to do that would be to bring that functionality
directly into our Sphinx extension, rewriting it in Python. An
alternative I have been considering, as a learning project that would
make me One Of The Cool Kids again, would be to do it in Rust instead.
For the time being, though, I wouldn't hold my breath for getting this
kind of improvement into kernel-doc. I wish I could say otherwise.
Thanks,
jon
next prev parent reply other threads:[~2025-01-02 18:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 11:39 [PATCH net-next v1 1/1] net: phy: Move callback comments from struct to kernel-doc section Oleksij Rempel
2024-12-06 12:14 ` Russell King (Oracle)
2024-12-07 20:38 ` Andrew Lunn
2024-12-10 11:56 ` Paolo Abeni
2024-12-10 14:02 ` Russell King (Oracle)
2024-12-10 14:37 ` Jakub Kicinski
2024-12-16 12:20 ` Oleksij Rempel
2024-12-17 1:53 ` Jakub Kicinski
2024-12-17 5:40 ` Oleksij Rempel
2024-12-17 15:03 ` Jakub Kicinski
2025-01-02 16:56 ` Russell King (Oracle)
2025-01-02 18:01 ` Jonathan Corbet [this message]
2025-01-02 18:28 ` Russell King (Oracle)
2024-12-10 12:03 ` Mateusz Polchlopek
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=87seq1xffx.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kernel@pengutronix.de \
--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=o.rempel@pengutronix.de \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).