[Ksummit-discuss] Topic: Removal of code that is still in use by users but there is a better code.

Roland Dreier roland at kernel.org
Wed Jun 11 22:26:12 UTC 2014

On Wed, Jun 11, 2014 at 3:17 PM, James Bottomley
<James.Bottomley at hansenpartnership.com> wrote:
> This would eventually become like CONFIG_EXPERIMENTAL before somebody
> put it out of its misery: a pointless thing which everybody enables.

Probably so.

> Could we just step back and ask what the burning need to do this (at
> least for drivers; I understand the ABI deprecation headache) is?  Most
> driver code for obsolete things harmlessly compiles; why bother trying
> to hunt them down and shoot them when they're not really causing
> offence?

Every time a developer wants to change a core API, that developer
needs to patch every driver that uses the API.  Every old, unused,
bitrotten driver we have in the tree is 100% wasted work, and often a
substantial amount of work because it's really hard even to understand
how those drivers are (mis)using the API being changed.

 - R.

More information about the Ksummit-discuss mailing list