From: Ondrej Zary <linux@zary.sk>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>, Tim Waugh <tim@cyberelk.net>,
linux-block@vger.kernel.org, linux-parport@lists.infradead.org
Subject: Re: [RFC] remove the paride driver
Date: Thu, 23 Dec 2021 23:34:46 +0100 [thread overview]
Message-ID: <202112232334.46631.linux@zary.sk> (raw)
In-Reply-To: <4f88a1e4-1bbb-1c32-79dd-389f18cb3fa4@kernel.dk>
On Thursday 23 December 2021 19:33:21 Jens Axboe wrote:
> On 12/23/21 10:29 AM, Ondrej Zary wrote:
> > On Thursday 23 December 2021 12:35:03 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.
> >>
> >> Ondrej: you're the last known users, so please speak up if you still
> >> have a use case!
> >
> > Looks like I really need to do the libata conversion.
>
> That would indeed be great! As mentioned in my reply, I don't want to
> remove drivers that are actively being used. Is the libata conversion
> something you are going to do, or is it more of a dream at this point?
> Ideally we get that done first, and then remove paride.
Haven't started yet. But I'm increasing its priority in my todo list.
--
Ondrej Zary
next prev parent reply other threads:[~2021-12-23 22:35 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 ` [RFC] remove the paride driver Jens Axboe
2021-12-23 17:29 ` Ondrej Zary
2021-12-23 18:33 ` Jens Axboe
2021-12-23 22:34 ` Ondrej Zary [this message]
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=202112232334.46631.linux@zary.sk \
--to=linux@zary.sk \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-parport@lists.infradead.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.