public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: david@lang.hm
Cc: Pavel Machek <pavel@ucw.cz>,
	linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH 1/4] strip: move driver to staging
Date: Mon, 26 Oct 2009 13:43:17 -0400	[thread overview]
Message-ID: <20091026174317.GG2792@tuxdriver.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0910261013430.11504@asgard.lang.hm>

On Mon, Oct 26, 2009 at 10:18:20AM -0700, david@lang.hm wrote:
> On Mon, 26 Oct 2009, John W. Linville wrote:

>> "ongoing maintenance for no clear benefit" -- that is what is wrong
>> with it.
>
> supporting existing hardware is no longer a 'clear benifit'?

Do you own or have access to such hardware?  If the hardware is
obsolete, unused, and mostly non-existant then what is the benefit
to maintaining a driver that is rotting?

> is this driver broken (as in not working)?

I have no idea.  I suspect that you don't know either.

> other than the fact that you don't think many people have this hardware,  
> is there anything wrong with this driver?

It sits there, bloating the target area for API maintenance and
providing a likely broken example of how to write Linux drivers.

> if this driver hasn't been changed other than for blanket API changes, 
> how is it causing significant problems?

It is a distraction for no clear (or even murky) benefit, one more
thing to keep compiling.

> if someone were to claim 'maintainership' and then do nothing other than  
> complain if someone else were to change an API but not fix this in the  
> process, how would this be different than the current situation?

Not much different, possibly worse if they created a bigger
distraction.  But if they actually had the hardware we might at least
be confident that the effort was in some way worthwhile...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-10-26 17:46 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20  5:17 [PATCH 1/4] strip: move driver to staging John W. Linville
2009-10-20  5:17 ` [PATCH 2/4] arlan: " John W. Linville
     [not found]   ` <1256015830-12700-3-git-send-email-linville@tuxdriver.com>
2009-10-20  5:17     ` [PATCH 4/4] netwave: " John W. Linville
2009-10-27 20:36       ` Staging: " Greg KH
2009-10-27 21:05         ` John W. Linville
2009-10-27 22:12           ` Greg KH
2009-10-20 16:06 ` [PATCH 1/4] strip: " Randy Dunlap
2009-10-26 16:46   ` John W. Linville
2009-10-26 17:02     ` Randy Dunlap
2009-10-26 18:48       ` Greg KH
2009-10-23 16:10 ` Pavel Machek
2009-10-23 16:54   ` Alan Cox
2009-10-26 16:55   ` John W. Linville
2009-10-26 17:18     ` david
2009-10-26 17:43       ` John W. Linville [this message]
2009-10-26 18:47       ` Greg KH
2009-10-27  4:17         ` david
2009-10-27  5:21           ` David Miller
2009-10-27  8:34           ` Stefan Richter
2009-10-27 14:08           ` Greg KH
2009-10-27 18:39             ` david
2009-10-27 20:38               ` Greg KH
2009-10-27 21:13               ` John W. Linville
2009-10-27 21:32               ` Alan Cox
2009-10-26 17:24     ` Pavel Machek
2009-10-26 17:29       ` Alan Cox
2009-10-26 17:34       ` John W. Linville
2009-10-26 18:48       ` Greg KH
2009-10-26 19:07         ` Joe Perches
2009-10-26 19:17           ` Greg KH
2009-10-26 19:20           ` John W. Linville
2009-10-26 19:36             ` Greg KH
2009-10-26 20:06             ` Joe Perches

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=20091026174317.GG2792@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=david@lang.hm \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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