From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753284AbdK1Mef (ORCPT ); Tue, 28 Nov 2017 07:34:35 -0500 Received: from mout.web.de ([212.227.15.14]:63656 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752357AbdK1Meb (ORCPT ); Tue, 28 Nov 2017 07:34:31 -0500 Subject: Re: ALSA: nm256: Fine-tuning for three function implementations To: Takashi Iwai , alsa-devel@alsa-project.org Cc: Arvind Yadav , Jaroslav Kysela , Takashi Sakamoto , kernel-janitors@vger.kernel.org, LKML References: <24f8c777-1eb4-e7e7-9371-79f32700c9dc@users.sourceforge.net> <2cbef557-5f89-c630-e108-14ef2ce6b41a@users.sourceforge.net> <1547a4c2-5b70-e3a3-b482-d28c538e615c@users.sourceforge.net> From: SF Markus Elfring Message-ID: Date: Tue, 28 Nov 2017 13:33:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:lV/7SUtXdizQ89c3wD9vuPi95A16KC96XQWxazR0CtelUaKjVGc bBN+KV1pMo2Rh8a/S7Gw2Pmt/iNmMyvX+xJCB0s+kNMo/eB6VmwIra2mIubfVLL5mirdZNM 9NVdcQvK6eJcudc3sCwS/oAUt9xdQlN4/4g3cCtzLgn69Lt0GfzUCxtp/7oOlojs/y77zC8 K9PWRbdEqvwy9rJZR3okg== X-UI-Out-Filterresults: notjunk:1;V01:K0:OfqWEEbhMkQ=:UvkDOl5bb4wlKIa2mzjf9d 2C82v8DzEwbQpKC8T0qBfTsuWLx6YwHDRXUPZmA6CbroLY81rZa7/W79+AI0lTwHbN1qN+nzH N2g368C6O8LH3IFthGFFdjFQIbiryOfdZ62Ql1zqQvBQKPLPj19XbjQ+UeigWhgE5+DSDwmsO Sv7bhzQX8SIyHObIRU3t7jJ5suiU3aEx84CpqGTC6hhy/ji9oxUnU5a3+94dUKAYbJIneSNsw QNrGFlnhGYacNSNVnt+loBRgRhi4SW9LXyslI3zabyOOjJG/N2FRlR+S+2SWPF41LgrEdXmmP lUZdsRhygoTtWeO2PHUb1P+QpeCYTochstUrf7i1JzwqnEq4m1tTyF9e2j9jC7lW7iKQcVK5j BowuEaHC5klgECfx8ydx61iQUscIGHmN4Tyf4zw/yXXGPdMF4UVeJyQpr4ISKP0Mfojh0FPcp aVC/qOwqL6fmbQylryN8/fEP2hZZqQcQNlnUGdxpSSr71anZgj1hXQB7HP3fWaf/URY75A6IM x7vpDiecAQPQWLiH27Z70/ApOkz2giAuDRmqMOF57miJTE8OnsLzrKF4HttS8Hq0t0XHnM13e 7VC2TWwyBodfH5vViFnKYwY135kkU2yBtuU/IYNEivIp7LMHWA1Jb4zSQqA9TbmhaVOS8lSza gIdvKyW6LCq0MT/BLkYALiIj4CVO7rLMZH7uiE4A6UrBInusjvV6+g1I0TTvuQIdUoDzkWuo4 SWilNMRP9sSYq+WAMw8BF686qMucelW7AXI3Eei+A5He3znAktcs63OwrdyvbPwfby26CZAuH ebMNlYwuG+hKEpQPgHuV24E9ZGZhLRy8H0qhW8s/FMUu/zfopM= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> It seems then that you can not get the kind of information you might be looking for >> at the moment from me (alone). > > No, the patch itself speaks. Are we still trying to clarify (only) two possible update steps for this software module? > If you get more reviewed-by from others, it means already it's safer > to apply. Then I can take it. How are the statistics for such tags in the sound subsystem? > But without that, it's obviously no material to take. Thanks for such an explanation of your current view. >> I hope that mailing list readers could offer something. > > Let's hope. Are any additional communication interfaces helpful? >> Did this software module become “too old”? > > Mostly the hardware is too old, Which time frames have you got in mind for acceptable software maintenance? > or the change itself isn't interesting enough. This is another general possibility. >> Can higher level transformation patterns become easier to accept >> by any other means? > > Only if it's assured to work and not to break anything else. Have you got any steps in mind for an improved “feeling” or “assurance”? >> How much does the omission of such an useful development tool >> influence your concerns? > > Can't judge unless I really see / use it. I find that there are some options to consider. >> Would you like to improve the software situation in any ways there? > > I *hope*, but only when it's not too annoying. Under which circumstances are you going to start working with a continuous integration system? Regards, Markus