From: Clemens Ladisch <clemens@ladisch.de>
To: Andreas Mohr <andi@lisas.de>, Takashi Iwai <tiwai@suse.de>
Cc: 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: Mon, 06 Oct 2014 21:41:20 +0200 [thread overview]
Message-ID: <5432F060.5060307@ladisch.de> (raw)
In-Reply-To: <20141006184150.GA2465@rhlx01.hs-esslingen.de>
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.
Regards,
Clemens
next prev parent reply other threads:[~2014-10-06 19:41 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 ` Clemens Ladisch [this message]
2014-10-07 10:44 ` [alsa-devel] Workable vintage driver support mechanism? (Re: " One Thousand Gnomes
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=5432F060.5060307@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=andi@lisas.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