public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Finn Thain <fthain@linux-m68k.org>, Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux SCSI <linux-scsi@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kernel Janitors <kernel-janitors@vger.kernel.org>,
	Oliver Neukum <oliver@neukum.org>, Ali Akcaagac <aliakc@web.de>,
	Jamie Lenehan <lenehan@twibble.org>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 3/3] Documentation: scsi: dc395x: Remove reference to 2.4 driver
Date: Fri, 05 May 2023 07:34:43 -0600	[thread overview]
Message-ID: <87pm7enbpo.fsf@meer.lwn.net> (raw)
In-Reply-To: <d919a2e1-5749-13f8-7867-1f17277190f4@linux-m68k.org>

Finn Thain <fthain@linux-m68k.org> writes:

> On Fri, 5 May 2023, Bagas Sanjaya wrote:
>
>> The 2.4 driver link returns 404. 
>
> It's still potentially useful:
> https://web.archive.org/web/20140129181343/http://www.garloff.de/kurt/linux/dc395/
>
>> As no one runs 2.4 kernel anymore,
>
> Would it make a difference if someone does run that? Were you planning to 
> delete the source code for the 2.4 kernel too?

Most of the 2.4 code has indeed been deleted *from current kernels*.
It's not clear to me why 2.4 documentation should be immune to that same
process.  If we keep every 20-year-old reference, our docs will be even
cruftier and less useful than they are now.

Thanks,

jon

  reply	other threads:[~2023-05-05 13:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05  8:27 [PATCH 0/3] dc395x stale reference cleanup Bagas Sanjaya
2023-05-05  8:27 ` [PATCH 1/3] MAINTAINERS: Drop DC395x list and site Bagas Sanjaya
2023-05-05  9:16   ` Dan Carpenter
2023-05-06  2:21     ` Bagas Sanjaya
2023-05-06 21:01   ` Ali Akcaagac
2023-05-05  8:27 ` [PATCH 2/3] Documentation: scsi: dc395x: Replace non-functional twibble.org list Bagas Sanjaya
2023-05-05  8:27 ` [PATCH 3/3] Documentation: scsi: dc395x: Remove reference to 2.4 driver Bagas Sanjaya
2023-05-05 10:12   ` Finn Thain
2023-05-05 13:34     ` Jonathan Corbet [this message]
2023-05-06  0:17       ` Finn Thain
2023-05-09  8:55       ` Oliver Neukum
2023-05-10  8:57         ` Bagas Sanjaya

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=87pm7enbpo.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=aliakc@web.de \
    --cc=bagasdotme@gmail.com \
    --cc=fthain@linux-m68k.org \
    --cc=jejb@linux.ibm.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lenehan@twibble.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=oliver@neukum.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