ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Ksummit-discuss] Topic: Removal of code that is still in use by users but there is a better code.
Date: Thu, 19 Jun 2014 15:01:16 +0200	[thread overview]
Message-ID: <CACRpkdYjJuVEOr7WHCojXtvszb0ZhuLuZAqh8DPdXCoNroUF9g@mail.gmail.com> (raw)
In-Reply-To: <1402526161.2523.79.camel@dabdike.int.hansenpartnership.com>

On Thu, Jun 12, 2014 at 12:36 AM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
> On Wed, 2014-06-11 at 15:26 -0700, Roland Dreier wrote:

>> 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.
>
> Well how often do we do that?  It's not like it's the most common
> activity.

Well I'm doing that right now in the GPIO subsystem where I'm
refactoring all local irqchip implementations into the gpiolib.

So I attack-patch all suitable refactoring targets, indeed. And
sometimes the answer comes back "I don't have that hardware
anymore, cannot test it", even from the person listed as maintainer.
(drivers/gpio/gpio-adnp.c, drivers/pinctrl/spear/*)

And then I get a strong urge to delete it, because a maintainer that
can't maintain is not much of a maintainer...

Yours,
Linus Walleij

  parent reply	other threads:[~2014-06-19 13:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 20:12 Konrad Rzeszutek Wilk
2014-06-10 20:19 ` H. Peter Anvin
2014-06-11  0:36   ` josh
2014-06-11 15:56     ` H. Peter Anvin
2014-06-11 20:02       ` josh
2014-06-11 17:54   ` Guenter Roeck
2014-06-11 19:43     ` Bjorn Helgaas
2014-06-11 21:53       ` Stephen Rothwell
2014-06-11 22:01         ` Andy Lutomirski
2014-06-11 22:17           ` James Bottomley
2014-06-11 22:26             ` Roland Dreier
2014-06-11 22:36               ` James Bottomley
2014-06-12 11:41                 ` Rafael J. Wysocki
2014-06-12 13:27                 ` John W. Linville
2014-06-13  1:36                   ` James Bottomley
2014-06-19 13:01                 ` Linus Walleij [this message]
2014-06-11 23:22       ` Guenter Roeck
2014-06-12  2:48         ` Steven Rostedt
2014-06-12  7:16           ` Geert Uytterhoeven
2014-06-12  0:07     ` H. Peter Anvin

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=CACRpkdYjJuVEOr7WHCojXtvszb0ZhuLuZAqh8DPdXCoNroUF9g@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=ksummit-discuss@lists.linuxfoundation.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