From: Jakub Kicinski <kuba@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@kernel.org>,
torvalds@linux-foundation.org, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, Thomas Osterried <thomas@osterried.de>
Subject: Re: Driver graveyard
Date: Mon, 2 May 2022 08:10:01 -0700 [thread overview]
Message-ID: <20220502081001.6135b370@kernel.org> (raw)
In-Reply-To: <87ee1cxb2o.fsf@meer.lwn.net>
On Mon, 02 May 2022 08:29:03 -0600 Jonathan Corbet wrote:
> Jakub Kicinski <kuba@kernel.org> writes:
>
> > Thomas suggested that it may be nice to create some form of a record
> > for drivers which were retired from the tree. I think a code-centric
> > equivalent of CREDITS could be a good idea.
> >
> > Does such a record already exist somewhere? If not any thoughts on
> > creating a file storing (Kconfig, short description, commit which
> > removed the driver)? E.g.
> >
> >
> > K: DMASCC
> > D: Hamradio high-speed (DMA) SCC driver for AX.25. Driver supported
> > D: Ottawa PI/PI2, Paccomm/Gracilis D: PackeTwin, and S5SCC/DMA boards.
> > C: 865e2eb08f51
>
> So what is the purpose for this file? And more to the point, I guess:
> is there a need for it to be strictly machine-readable? If the
> objective is to remember our history to minimize our chances of
> repeating it, something more prose-oriented might work better.
To be honest I found the existence of the CREDITS file useful when
removing stale MAINTAINERS entries. A move seems less hostile than
a erasure (using a very broad definition of "move" in case of drivers).
Anything that makes people feel more at ease when I remove their driver
would be helpful.
The only practical (i.e. not armchair-psychology-based) use I can think
of is if someone is about to sit down and write a new driver they may
grep the tree for the name of the HW, and they may find the graveyard
entry. So I think listing the exact HW supported is useful. That said
as I'm writing this I'm reminded how old the hypothetical HW in the
previous sentence likely is.
I used the machine-readable format following CREDITS. I figured CREDITS
serves no practical purpose either today, in hindsight that's a bit
ahistoric.
next prev parent reply other threads:[~2022-05-02 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 14:18 Driver graveyard Jakub Kicinski
2022-05-02 14:29 ` Jonathan Corbet
2022-05-02 15:10 ` Jakub Kicinski [this message]
2022-05-02 15:15 ` Juergen Gross
2022-05-02 15:18 ` Laurent Pinchart
2022-05-02 15:33 ` Arnd Bergmann
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=20220502081001.6135b370@kernel.org \
--to=kuba@kernel.org \
--cc=arnd@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=thomas@osterried.de \
--cc=torvalds@linux-foundation.org \
--cc=workflows@vger.kernel.org \
/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).