linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jakub Kicinski <kuba@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@kernel.org>,
	torvalds@linux-foundation.org
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	Thomas Osterried <thomas@osterried.de>
Subject: Re: Driver graveyard
Date: Mon, 02 May 2022 08:29:03 -0600	[thread overview]
Message-ID: <87ee1cxb2o.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220502071818.5101c752@kernel.org>

Jakub Kicinski <kuba@kernel.org> writes:

> Hi!
>
> 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.

Thanks,

jon

  reply	other threads:[~2022-05-02 14:29 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 [this message]
2022-05-02 15:10   ` Jakub Kicinski
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=87ee1cxb2o.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=arnd@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.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).