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>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 0/3] dc395x stale reference cleanup
Date: Fri, 5 May 2023 15:27:01 +0700 [thread overview]
Message-ID: <20230505082704.16228-1-bagasdotme@gmail.com> (raw)
A small stale reference cleanup series for DC395x driver. The shortlog
below should be self-explanatory.
This series is based on for-next branch of scsi tree, but can be applied
to fixes if needed.
Bagas Sanjaya (3):
MAINTAINERS: Drop DC395x list and site
Documentation: scsi: dc395x: Replace non-functional twibble.org list
Documentation: scsi: dc395x: Remove reference to 2.4 driver
Documentation/scsi/dc395x.rst | 9 ++-------
MAINTAINERS | 4 +---
2 files changed, 3 insertions(+), 10 deletions(-)
base-commit: d1316c7b9ec3683c4ca531234998c0e5b9e9447c
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-05-05 8:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 8:27 Bagas Sanjaya [this message]
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
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=20230505082704.16228-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=aliakc@web.de \
--cc=corbet@lwn.net \
--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