From: Phillip Potter <phil@philpotter.co.uk>
To: Jens Axboe <axboe@kernel.dk>, Enze Li <lienze@kylinos.cn>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] cdrom: do not print info list when there is no cdrom device
Date: Mon, 18 Apr 2022 22:04:18 +0100 [thread overview]
Message-ID: <Yl3SUr9+qzoRlQt8@equinox> (raw)
In-Reply-To: <226c4072-a3ca-a5a4-1b7f-f7104b43af03@kernel.dk>
On Mon, Apr 11, 2022 at 10:51:28AM -0600, Jens Axboe wrote:
> > 20 -- Modify sysctl/proc interface. I plan on having one directory per
> > 21 drive, with entries for outputing general drive information, and sysctl
> > 22 based tunable parameters such as whether the tray should auto-close for
> > 23 that drive. Suggestions (or patches) for this welcome!
> > ================================================
> > I'd like to know if the relevant patches are still welcome?
> >
> > IIUC, the TODO List says that we need to implement a modification of the
> > following form:
> > ----------------------------------------------------------------------------------------------------------
> > $ tree /proc/sys/dev/cdrom
> > /proc/sys/dev/cdrom
> > |--sr0--autoclose
> > | |-autoeject
> > | |-check_media
> > | |-debug
> > | |-info
> > | |-lock
> > |
> > |--sr1--autoclose
> > | |-autoeject
> > | |-check_media
> > | |-debug
> > | |-info
> > | |-lock
> > |
> > |--sr2 ...
> > .
> > .
> > .
> > ----------------------------------------------------------------------------------------------------------
> > I would appreciate it if you could give me some advice.
>
> Let's not do that, this advice is perhaps 20 years old. /proc isn't to
> be used for anything like that these days.
>
> --
> Jens Axboe
>
Hi Both,
I will send a patch alongside others during the next merge window to
remove this TODO section for now. It was part of the initial mainline
git commit (17 years and two days ago), so it (as Jens says) is almost
certainly even older than this.
Regards,
Phil
prev parent reply other threads:[~2022-04-18 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 8:42 [PATCH] cdrom: do not print info list when there is no cdrom device Enze Li
2022-04-08 12:34 ` Jens Axboe
2022-04-09 4:25 ` Enze Li
2022-04-09 8:16 ` Phillip Potter
[not found] ` <f74b6933-5357-6b2c-3127-7a3465dadbdf@kylinos.cn>
2022-04-11 16:51 ` Jens Axboe
2022-04-18 21:04 ` Phillip Potter [this message]
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=Yl3SUr9+qzoRlQt8@equinox \
--to=phil@philpotter.co.uk \
--cc=axboe@kernel.dk \
--cc=lienze@kylinos.cn \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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