Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp674204rwr; Fri, 5 May 2023 03:23:46 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4Dl3Sk+hNXqZWglb6EFWO3a+bD/Z4gjfB3mRwWsRv2Qky2VxtZx4KiEnr30bLkzNwkS2G2 X-Received: by 2002:a17:90b:3594:b0:24d:e048:398b with SMTP id mm20-20020a17090b359400b0024de048398bmr1020984pjb.14.1683282226286; Fri, 05 May 2023 03:23:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683282226; cv=none; d=google.com; s=arc-20160816; b=BJ6SeY40Eq2L+JH3Uv3HdaVdUCHwDSNJ4JwceicRl+68bqwLSAVr67YDIpwnzL40Od DXCNcUXhdGxRPNFDIKjrAQ+JCuUaG9lY757g89QMJ17FUi17hWqV2x3nwVZGWKOnxou+ qJm39ZAvZkktAhmb3qXpoo/Z1CIUr1T0wynJbHLm/rcB/K73NxW73g3s0wi2tsl5Sxvz Fl+Nd7HWsK62ro/QAF9tg6fNxyhN5sZyqR8pA9asxaovBpnD5pGrz5HwHptLDlq9NdHF IJp1rYtYn6DOd0VTeVfA1gxVcnbVFJ1to3XOXA7BDfwkg00qyWmy56pwIPsqD1JSZcRG deHg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date:feedback-id:dkim-signature; bh=V4D6xLrOnK5kaemJE3ljBJy5a0XXQgxZIK3WV5Xq8Vo=; b=pqfP6kekWE4vZdFpR7K2qZMktZA5QG7Am27zxV4x3ABbLjOm+EPBU7LDWU2m5JTWAA Esc3OLDaTIufPASYq4wA++5JlPzTTesIMRPSlE7sS1V1MicrpuW3dxGjoDuGhZCjRJIo 17iQShdqzdtwTmc7PRpdgMfoewoGRjuW7kAx/3wN/OAK1bcx2Y4x3EVjraXt6H/ae1+J AKvfWOpWj+Nhk+BPt5+zr3OVMMvVuGH4eoF4s/4NjykLtNSSCx8SzwtFpXrKzHboxm+X GnPSrnSYqJhA3GDnUuckY5YNT2X/uKs7FlUymymdteDCJk9rXBjz77QXDEBFR2ttsiKY kC6A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b="ZeqM/lCh"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s16-20020a170902b19000b001aaed82c2afsi1348769plr.171.2023.05.05.03.23.28; Fri, 05 May 2023 03:23:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b="ZeqM/lCh"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231641AbjEEKIT (ORCPT + 99 others); Fri, 5 May 2023 06:08:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33484 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229441AbjEEKIS (ORCPT ); Fri, 5 May 2023 06:08:18 -0400 Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E902813859; Fri, 5 May 2023 03:08:16 -0700 (PDT) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 8F2165C028C; Fri, 5 May 2023 06:08:14 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 05 May 2023 06:08:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1683281294; x=1683367694; bh=V4D6xLrOnK5ka emJE3ljBJy5a0XXQgxZIK3WV5Xq8Vo=; b=ZeqM/lChYCWtP5MuNAloVu5jSa7pW 9EaB8Ti9632juuvtWwdhVdcUkFa0+vWz8zuI2mHh7ys8X3YlYs4Ls0CQBEmgrKoJ DSZqQngcz8Vb8HhmR3Qq0pqGfO8MdJngDKwF7gL8yAjN+xdMk1NyoPyygIykXj+g jeqLX6huhwyQqjR+DLhnAwRY5fd9ux8jM94r0Diao2M1NIGmkCFqOIRMBHqVGtNW ZkxayzR2Rl+teGzFMLyO5s7bTlo3qwShGr6h5w9scDgk+MRXl7sYD9GqtsFME7nT 86C8vOHXY1NeSvThG9zQojWjYdyxmMwAdYNsE4NOkzpOOR5EFACYyTK3g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeefvddgvdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevufgjkfhfgggtsehttdertddttddvnecuhfhrohhmpefhihhnnhcu vfhhrghinhcuoehfthhhrghinheslhhinhhugidqmheikehkrdhorhhgqeenucggtffrrg htthgvrhhnpeeuiefguedvuedtveduffegieehkeejjedttddvvedtvdfhueduhfeifedt teehhfenucffohhmrghinheprghrtghhihhvvgdrohhrghdpghgrrhhlohhffhdruggvne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepfhhthhgr ihhnsehlihhnuhigqdhmieekkhdrohhrgh X-ME-Proxy: Feedback-ID: i58a146ae:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 5 May 2023 06:08:10 -0400 (EDT) Date: Fri, 5 May 2023 20:12:08 +1000 (AEST) From: Finn Thain To: Bagas Sanjaya cc: Linux SCSI , Linux Documentation , Linux Kernel Mailing List , Linux Kernel Janitors , Oliver Neukum , Ali Akcaagac , Jamie Lenehan , Jonathan Corbet , "James E.J. Bottomley" , "Martin K. Petersen" Subject: Re: [PATCH 3/3] Documentation: scsi: dc395x: Remove reference to 2.4 driver In-Reply-To: <20230505082704.16228-4-bagasdotme@gmail.com> Message-ID: References: <20230505082704.16228-1-bagasdotme@gmail.com> <20230505082704.16228-4-bagasdotme@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? > remove the stale reference. > It was always stale inasmuch as it is apparently there to give credit for prior contributions, plus a changelog (see archive.org). Any published link should probably be accompanied by a "retrieved on yyyy-mm-dd" qualification. But no qualification is better than no link at all, IMO. Of course, there is a reason for an edit here. Yet it's not the one you gave. "This is a 2.5 only driver" is simply incorrect. (If it was correct you'd get to delete the whole thing.) This is not a nak as I'm not the maintainer. But this patch just looks like churn with no justification. Perhaps I'm not the only one who can't see it. > Signed-off-by: Bagas Sanjaya > --- > Documentation/scsi/dc395x.rst | 4 ---- > 1 file changed, 4 deletions(-) > > diff --git a/Documentation/scsi/dc395x.rst b/Documentation/scsi/dc395x.rst > index c413b629809bcd..a6320561543650 100644 > --- a/Documentation/scsi/dc395x.rst > +++ b/Documentation/scsi/dc395x.rst > @@ -11,10 +11,6 @@ be safe to use. Testing with hard disks has not been done to any > great degree and caution should be exercised if you want to attempt > to use this driver with hard disks. > > -This is a 2.5 only driver. For a 2.4 driver please see the original > -driver (which this driver started from) at > -http://www.garloff.de/kurt/linux/dc395/ > - > Problems, questions and patches should be submitted to the `Linux SCSI > mailing list `_. > >