linux-kernel - Re: ALSA: bebob: Use common error handling code in snd_bebob_stream_start

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <8e2bbd25-d8d0-0d7b-2d4e-daf495bd523f@sakamocchi.jp>
Date:   Wed, 27 Sep 2017 20:09:31 +0900
From:   Takashi Sakamoto <o-takashi@...amocchi.jp>
To:     SF Markus Elfring <elfring@...rs.sourceforge.net>,
        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()

On Sep 27 2017 15:38, SF Markus Elfring wrote:
>> 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?

Please don't ignore the practicality I've explained, and don't 
accumulate your questions without it.


Regards

Takashi Sakamoto