From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752229AbdI0LJl (ORCPT <rfc822;w@1wt.eu>);
        Wed, 27 Sep 2017 07:09:41 -0400
Received: from smtp-proxy004.phy.lolipop.jp ([157.7.104.45]:54211 "EHLO
        smtp-proxy004.phy.lolipop.jp" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1750703AbdI0LJj (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 27 Sep 2017 07:09:39 -0400
Subject: Re: ALSA: bebob: Use common error handling code in
 snd_bebob_stream_start_duplex()
To: SF Markus Elfring <elfring@users.sourceforge.net>,
        alsa-devel@alsa-project.org
Cc: Clemens Ladisch <clemens@ladisch.de>, Jaroslav Kysela <perex@perex.cz>,
        Takashi Iwai <tiwai@suse.com>, kernel-janitors@vger.kernel.org,
        LKML <linux-kernel@vger.kernel.org>
References: <85f95150-9cec-7a53-7692-837ba543e1ec@users.sourceforge.net>
 <541f0f9f-fc87-f65b-bbd8-fec5d45d5d2e@users.sourceforge.net>
 <a1dee732-f5c4-5b35-9f82-553fc8ce430d@sakamocchi.jp>
 <3afecbef-b7ac-a4e8-f439-a351916f05e5@users.sourceforge.net>
 <09bb0e83-01fe-cd12-a084-31db3f12d663@sakamocchi.jp>
 <06a8e3ee-c3c3-b4c7-0cf9-69a2efdaf0ba@users.sourceforge.net>
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Message-ID: <8e2bbd25-d8d0-0d7b-2d4e-daf495bd523f@sakamocchi.jp>
Date: Wed, 27 Sep 2017 20:09:31 +0900
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <06a8e3ee-c3c3-b4c7-0cf9-69a2efdaf0ba@users.sourceforge.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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