From: Christoph Hellwig <hch@lst.de>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: Christoph Hellwig <hch@lst.de>,
axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RFC] block: remove the paride drivers
Date: Thu, 15 Mar 2018 09:04:55 +0100 [thread overview]
Message-ID: <20180315080455.GA12388@lst.de> (raw)
In-Reply-To: <201803150904.25087.linux@rainbow-software.org>
On Thu, Mar 15, 2018 at 09:04:24AM +0100, Ondrej Zary wrote:
> On Thursday 15 March 2018, Christoph Hellwig wrote:
> > The paride drivers are some of the cruftiest, grottiest block drivers
> > (besides drivers/ide and floppy.c) and have seen one single targeted
> > commit since the dawn of git in 2007. Drop them to make block layer
> > improvements easier.
>
> This will make my parallel port ZIP and LS-120 drives useless :(
So you are still using them and the code actually works properly?
next prev parent reply other threads:[~2018-03-15 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 7:52 [PATCH, RFC] block: remove the paride drivers Christoph Hellwig
2018-03-15 8:04 ` Ondrej Zary
2018-03-15 8:04 ` Christoph Hellwig [this message]
2018-03-15 22:04 ` Ondrej Zary
2018-03-15 22:17 ` Ondrej Zary
2018-03-15 22:37 ` Ondrej Zary
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=20180315080455.GA12388@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.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