[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <06a8e3ee-c3c3-b4c7-0cf9-69a2efdaf0ba@users.sourceforge.net>
Date: Wed, 27 Sep 2017 08:38:48 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Takashi Sakamoto <o-takashi@...amocchi.jp>,
alsa-devel@...a-project.org
Cc: Clemens Ladisch <clemens@...isch.de>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, kernel-janitors@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: ALSA: bebob: Use common error handling code in
snd_bebob_stream_start_duplex()
> As long as I know, the last product with this solution was shipped
> at 2010. Thus the driver is under maintenance.
Thanks for your information.
> I have some tasks for this driver as well as drivers in ALSA firewire stack,
> however basically this driver is under maintenance and might not get
> further integration.
Good to know in principle …
> I think that code cleanup for the driver don't help the other developers.
I thought in an other direction if other contributors would like to care
for longer term support.
> It's better to apply such cleanup to more long-live codes such as
> core functionality of ALSA.
I am trying another general transformation pattern out.
> In this point of view, whether your patchset is worth to be applied
> or not, Please keep enough time to think about.
Automatic source code analysis can find various update candidates.
I am just unsure if a bit more software development attention is still
appropriate at some places.
Do you find any of the affected software modules so outdated
so that they should not be touched any more?
Regards,
Markus
Powered by blists - more mailing lists