From: Jens Axboe <email@example.com>
To: firstname.lastname@example.org, LKML <email@example.com>
Subject: Wanted: CDROM maintainer
Date: Fri, 27 Aug 2021 08:10:22 -0600 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Back in 1998, if I recall correctly, Erik Andersen posted on lkml that
he was looking for someone to take over development and maintainership
of the cdrom drivers. I responded to that, and ended up maintaining and
continuing the development of that part of the kernel. Outside of
working on that part of the stack, it eventually led to diving further
down the rabbit hole and into the general block IO stack. In many ways,
it kick started by career in kernel development.
These days I've got a lot on my plate, and areas like cdrom have been
neglected as a result. This obviously isn't an area of hot development
these days, but even so it still needs someone that cares for the code
and is available to review and merge patches in a timely fashion. I
haven't been able to do so for quite a while.
In the spirit of passing on the baton, I think we're way overdue for
some new blood in this area. With the recent removal of the old parallel
IDE code, the old atapi cdrom driver is gone. Hence there are really two
parts to this these days:
1) drivers/scsi/sr.c - the SCSI cdrom driver. My suggestion would be to
fold this in with general SCSI maintainership, as that's really where
2) drivers/cdrom/cdrom.c - the uniform cdrom layer. This is really the
meat of it. sr is a consumer, and so is the paride cdrom driver and
the sega dreamcast cdrom driver.
If you have any interest and experience with cdrom/dvd and mmc/atapi, I
would love to hear from you. Let's find a new good home for this code.
next reply other threads:[~2021-08-27 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 14:10 Jens Axboe [this message]
2021-08-27 23:56 ` Wanted: CDROM maintainer Phillip Potter
2021-09-03 14:09 ` Jens Axboe
2021-09-03 18:37 ` Phillip Potter
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).