Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Andreas Mohr <andi@lisas.de>, Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org,
	Ondrej Zary <linux@rainbow-software.org>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] Workable vintage driver support mechanism? (Re: [PATCH v3] ES938 support for ES18xx driver)
Date: Tue, 7 Oct 2014 11:44:47 +0100	[thread overview]
Message-ID: <20141007114447.35379ef7@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <5432F060.5060307@ladisch.de>

On Mon, 06 Oct 2014 21:41:20 +0200
Clemens Ladisch <clemens@ladisch.de> wrote:

> Andreas Mohr wrote:
> > I think I have an idea which might be useful to accept:
> > for every piece of sufficiently "vintage" submission,
> > people would be tasked with offering (or somehow ensuring)
> > a sufficiently closely time-related cleanup in other places.
> 
> The problem that such a new driver imposes is not a one-time reduction
> in overall kernel quality, but the ongoing maintenance effort.

Vintage is not IMHO a useful test. We have plenty of vintage hardware
with active hands-on maintainers which causes no problem, and plenty of
modern drivers with basically no maintainer that causes endless problems.

I think there is much merit in the Debian approach - if it's not got a
maintainer, and nobody is willing to take it on, throw it out. If it's
got a maintainer leave it in.

Economics will resolve the rest of the problem reasonably efficiently. If
someone cares enough about using it then they'll figure out how to keep
it maintained.

Alan

  reply	other threads:[~2014-10-07 10:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29 21:44 [PATCH v3] ES938 support for ES18xx driver Ondrej Zary
2014-09-29 21:58 ` Andreas Mohr
2014-10-06  9:39 ` [alsa-devel] " Takashi Iwai
2014-10-06 13:55   ` Ondrej Zary
2014-10-06 14:13     ` Takashi Iwai
2014-10-06 18:41       ` Workable vintage driver support mechanism? (Re: [alsa-devel] [PATCH v3] ES938 support for ES18xx driver) Andreas Mohr
2014-10-06 19:41         ` [alsa-devel] Workable vintage driver support mechanism? (Re: " Clemens Ladisch
2014-10-07 10:44           ` One Thousand Gnomes [this message]
2014-10-07  5:32         ` Takashi Iwai
2014-10-12 21:19           ` Ondrej Zary
2014-10-13  5:54             ` Workable vintage driver support mechanism? (Re: [alsa-devel] " Takashi Iwai

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=20141007114447.35379ef7@alan.etchedpixels.co.uk \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=andi@lisas.de \
    --cc=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rainbow-software.org \
    --cc=tiwai@suse.de \
    /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