From: David Miller <davem@davemloft.net>
To: b.zolnierkie@samsung.com
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
tj@kernel.org, gnomes@lxorguk.ukuu.org.uk,
sergei.shtylyov@cogentembedded.com
Subject: Re: [RFC PATCH 00/19] ide: remove deprecated host drivers (part 1)
Date: Thu, 08 Dec 2016 11:39:57 -0500 (EST) [thread overview]
Message-ID: <20161208.113957.686350007074631834.davem@davemloft.net> (raw)
In-Reply-To: <5007114.YSRHeGyTgl@amdc3058>
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Date: Thu, 08 Dec 2016 17:15:16 +0100
> On Thursday, December 08, 2016 10:23:08 AM David Miller wrote:
>> From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
>> Date: Thu, 08 Dec 2016 14:42:12 +0100
>>
>> > Ping.. since there was no negative (or any other) feedback I think that
>> > this can be put into -next for some wider exposure..
>>
>> I'm not going to apply this and break things on people, sorry.
>
> People building their own kernels with their own kernel config files
> and still using IDE drivers (deprecated in 2009 BTW) will have to
> update their setups to libata but otherwise nothing is supposed to
> break. So could you please explain in more detail what do you mean
> by "break things on people"?
There is no proof that the PATA drivers work %100 reliably as well as
the IDE driver they replace for every possible chip and architecture.
Therefore the only safe thing is to keep the IDE drivers around
forever.
They are not a maintainence burdon, I rarely get more than 1 patch
each merge window and most of the time those are cleanups or for the
handling of a kernel wide API change rather than bug fixes.
next prev parent reply other threads:[~2016-12-08 16:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 13:43 [RFC PATCH 00/19] ide: remove deprecated host drivers (part 1) Bartlomiej Zolnierkiewicz
2016-02-04 13:43 ` [RFC PATCH 01/19] ide: remove deprecated atiixp host driver Bartlomiej Zolnierkiewicz
2016-02-04 13:43 ` [RFC PATCH 02/19] ide: remove deprecated cs5520 " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 03/19] ide: remove deprecated cs5530 " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 04/19] ide: remove deprecated cs5535 " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 05/19] ide: remove deprecated cs5536 " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 06/19] ide: remove deprecated sc1200 " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 07/19] ide: remove deprecated delkin_cb " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 08/19] ide: remove deprecated it8213 " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 09/19] ide: remove deprecated it821x " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 10/19] ide: remove deprecated jmicron " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 11/19] ide: remove deprecated opti621 " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 12/19] ide: remove deprecated pdc202xx_old " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 13/19] ide: remove deprecated rz1000 " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 14/19] ide: remove deprecated serverworks " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 15/19] ide: remove deprecated sis5513 " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 16/19] ide: remove deprecated slc90e66 " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 17/19] ide: remove deprecated triflex " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RFC PATCH 18/19] ide: remove deprecated ide-pnp " Bartlomiej Zolnierkiewicz
2016-02-04 13:44 ` [RC PATCH 19/19] ide: remove deprecated icside " Bartlomiej Zolnierkiewicz
2016-07-08 17:07 ` [RFC PATCH 00/19] ide: remove deprecated host drivers (part 1) Bartlomiej Zolnierkiewicz
2016-12-08 13:42 ` Bartlomiej Zolnierkiewicz
2016-12-08 15:23 ` David Miller
2016-12-08 16:15 ` Bartlomiej Zolnierkiewicz
2016-12-08 16:39 ` David Miller [this message]
2016-12-08 17:11 ` Christoph Hellwig
2016-12-08 17:14 ` Bartlomiej Zolnierkiewicz
2016-12-08 17:58 ` David Miller
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=20161208.113957.686350007074631834.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=b.zolnierkie@samsung.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=tj@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