From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: Tim Waugh <tim@cyberelk.net>,
Ondrej Zary <linux@rainbow-software.org>,
linux-block@vger.kernel.org, linux-parport@lists.infradead.org
Subject: Re: [RFC] remove the paride driver
Date: Thu, 23 Dec 2021 07:17:53 -0700 [thread overview]
Message-ID: <f40e5fb7-c311-63e9-e9c7-02e2e2bc6e1d@kernel.dk> (raw)
In-Reply-To: <20211223113504.1117836-1-hch@lst.de>
On 12/23/21 4:35 AM, Christoph Hellwig wrote:
> Hi Jens,
>
> the paride driver has been unmaintained for a while and is a significant
> maintainance burden, including the fact that it is one of the last
> users of the block layer bounce buffering code. This patch suggest
> to remove it assuming no users complain loduly.
It really should be removed imho. To give folks a chance to pipe up,
might be more reasonable to queue it up post the 5.17 merge window. I
expect a lot of people are going to be less attentive the next few weeks
than usual, and that really isn't a lot of warning to give even with an
-rc8 planned.
--
Jens Axboe
next prev parent reply other threads:[~2021-12-23 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 11:35 [RFC] remove the paride driver Christoph Hellwig
[not found] ` <20211223113504.1117836-2-hch@lst.de>
2021-12-23 14:16 ` [PATCH] block: remove paride Jens Axboe
2021-12-24 6:00 ` Christoph Hellwig
2021-12-23 14:17 ` Jens Axboe [this message]
2021-12-23 17:29 ` [RFC] remove the paride driver Ondrej Zary
2021-12-23 18:33 ` Jens Axboe
2021-12-23 22:34 ` Ondrej Zary
2021-12-24 5:56 ` Christoph Hellwig
2022-01-30 20:14 ` Ondrej Zary
2022-02-02 14:13 ` Christoph Hellwig
2022-02-02 23:27 ` Damien Le Moal
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=f40e5fb7-c311-63e9-e9c7-02e2e2bc6e1d@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=linux@rainbow-software.org \
--cc=tim@cyberelk.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.