From: "John W. Linville" <linville@tuxdriver.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH 1/4] strip: move driver to staging
Date: Mon, 26 Oct 2009 12:55:19 -0400 [thread overview]
Message-ID: <20091026165518.GE2792@tuxdriver.com> (raw)
In-Reply-To: <20091023161006.GA1580@ucw.cz>
On Fri, Oct 23, 2009 at 06:10:06PM +0200, Pavel Machek wrote:
> On Tue 2009-10-20 14:17:07, John W. Linville wrote:
> > Move the strip ("Starmode Radio IP") driver to drivers/staging. For
> > several years this driver has only seen API "bombing-run" changes, and
> > few people ever had the hardware. This driver represents unnecessary
> > ongoing maintenance for no clear benefit.
>
> This seems like abuse of the staging process.
My mailbox has been filling-up with discussions of using staging like
this for the past few weeks. I'm reasonably certain those threads
were on the public lists.
> There's no TODO to say what needs to be fixed. You just don't want to
> maintain it. Because there's nothing to fix, noone has reason to patch
> it, and the (working, good enough) driver will just be removed.
"ongoing maintenance for no clear benefit" -- that is what is wrong
with it.
> It also marks driver as broken when it is not...
I didn't mark it broken, I proposed moving it to staging. As for
whether or not it actually is broken, how do you know?
The drivers in this thread are for pre-802.11 devices -- old ones
(e.g. ISA) at that. If we actually have users that are willing
to maintain them then maybe that is fine. But I don't see the
benefit of maintaining these simply as extra targets for API change
"bombing runs"...
> What about removing it in the regular way, that's
> Documentation/feature-removal.txt ?
This has been discussed recently as an alternative for unmaintained
drivers. I suspect this is better than adding a note to a file that
no one reads...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-10-26 17:01 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 [this message]
2009-10-26 17:18 ` david
2009-10-26 17:43 ` John W. Linville
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=20091026165518.GE2792@tuxdriver.com \
--to=linville@tuxdriver.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.