From: Bagas Sanjaya <bagasdotme@gmail.com>
To: 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>
Cc: Oliver Neukum <oliver@neukum.org>, Ali Akcaagac <aliakc@web.de>,
Jamie Lenehan <lenehan@twibble.org>,
Jonathan Corbet <corbet@lwn.net>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH v2 1/3] MAINTAINERS: Drop DC395x list and site
Date: Wed, 10 May 2023 16:39:31 +0700 [thread overview]
Message-ID: <20230510093933.19985-2-bagasdotme@gmail.com> (raw)
In-Reply-To: <20230510093933.19985-1-bagasdotme@gmail.com>
Emails to DC395x list bounce (550 error) and visiting the site returns
404 page.
Drop both twibble.org links. The driver should now be covered by
linux-scsi list.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
MAINTAINERS | 3 ---
1 file changed, 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7e0b87d5aa2e57..ca88932ee04e2f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5716,10 +5716,7 @@ DC395x SCSI driver
M: Oliver Neukum <oliver@neukum.org>
M: Ali Akcaagac <aliakc@web.de>
M: Jamie Lenehan <lenehan@twibble.org>
-L: dc395x@twibble.org
S: Maintained
-W: http://twibble.org/dist/dc395x/
-W: http://lists.twibble.org/mailman/listinfo/dc395x/
F: Documentation/scsi/dc395x.rst
F: drivers/scsi/dc395x.*
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-05-10 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 9:39 [PATCH v2 0/3] dc395x stale reference cleanup Bagas Sanjaya
2023-05-10 9:39 ` Bagas Sanjaya [this message]
2023-05-10 9:39 ` [PATCH v2 2/3] Documentation: scsi: dc395x: Replace non-functional twibble.org list Bagas Sanjaya
2023-05-10 9:39 ` [PATCH v2 3/3] Documentation: scsi: dc395x: Reword original driver attribution Bagas Sanjaya
2023-05-17 1:47 ` [PATCH v2 0/3] dc395x stale reference cleanup Martin K. Petersen
2023-05-22 22:46 ` Martin K. Petersen
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=20230510093933.19985-2-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=aliakc@web.de \
--cc=corbet@lwn.net \
--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=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