From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754210AbdK1UTb (ORCPT ); Tue, 28 Nov 2017 15:19:31 -0500 Received: from mout.web.de ([212.227.15.3]:57985 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753112AbdK1UT3 (ORCPT ); Tue, 28 Nov 2017 15:19:29 -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: <3b7b24bd-4bdf-752e-1a62-cc71e9152acc@users.sourceforge.net> <6da7e6dc-b181-d26c-9f09-6592469193be@users.sourceforge.net> <99282c06-bfad-d7cf-16d8-eb1e015ebdbd@users.sourceforge.net> <19724fa4-47eb-827c-cb17-126440500179@users.sourceforge.net> <727d5044-bad0-5170-83c0-dfddcc919588@users.sourceforge.net> <68fd71f5-a3e5-dbb7-d0d9-f9844fabe6c8@users.sourceforge.net> From: SF Markus Elfring Message-ID: Date: Tue, 28 Nov 2017 21:18:01 +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: 7bit X-Provags-ID: V03:K0:gWUq46vW6r38hmrh8RviEkAr32mzLt54NBuja/n4RMq2bMPVN+M GwqgLoFvh8HEfgYezEBXBP7RfbiYGA3JjDg6tqsBKoZM/yR38yoz0nLW+pln+JIkzuBvKoP Lvb4bNhvDlQ/AphCgFpJKf0R1bn23az8xzBel9paB6K6/FNY3jWoDvs2Aj1tthSGufgMXHu aqlRge3+5tmY2rEMdcdLg== X-UI-Out-Filterresults: notjunk:1;V01:K0:x3fm7S9Hs4M=:01G4ZHTp/vTcVLmPu4t6hP Xxs2Q/Q/omRyjllfavyy/Ux6n1loDU5qoMJ2BKt+8FsEeIv0fuiDxWcuPV64I+UGiRZ+luIDi BxfZA6c2zj2WQXqPnCytAbdzjaOB8On0fRwb8B9UMka0v/BUuWB1l6TLFmeIufgQFGGtRo0bA REb//YUk8Ry2PgmpbX3cADt6oLvaLge8srayW3CizhWNsPH0Cczp6X816ImFQ3RIHZwTXCbL8 pmbqm9nDmwfzdbYhriIDRnPa4qrMDgurvFZEAdXNrBkKNqLFc8zbsGZanmRLY3qtsYIN3hi9N kw9o/gRMX48EfC5SwUFmT8UrT7WJDJStzkIGSm2hAguxPuPLoAIslok5aUldQ6BFWjU7aC/Mf DmjcCCy8n9TeyVOWxjTunKH1piztj5zQishcPaL5JA0rur1JtvhncGmt5uh8n/58qkXsnx8yR xcyF6PjZ1tZArlqXRfribxlsYrqtJA51FIrD4YsJ6OzR6uDXKE9PJZeNlwkBjvobAfRZ5NK2Q oJeViUHxt2ZDpdTQi9SVOYXkQnwH5/5wssaTLmiOhPfVv0PXMZtzmmJKXPrPPhwMMye+UJHmf xO08Y4uifJVqYD14vjCiht963wzb+yzC7hD04RWbkw8w0KqgJ+lxeFCYCjs6HbzdbQUG6c13+ H+zgvwIxahiLbQMnwTovtESjNdSoEI+tJlyZbIBHQ9rZnq7b+VJPxAMw2OQlZq9CCHM9ZTDUD cUI7RGhxoZwR9a8x1ioT0JD0ADQslkcjHam2Vjf3sVyiMC/1N3+nIRKkaB5iOyY25kzuY+QsH aP5snAyYt/qtnXhbQkgW7g4lb2DVUw9PvovF8rMHC7hmcDI3nXzhUCmDJ1jKd07XUjM2KsS Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> Would you like to discuss the circumstances for the one glitch >> to which you might refer to? > > No need for discussion. I disagree to this view again. > It's difficult to recover a lost trust. I can follow this view to some degree. But I find that the current might point also other weaknesses out in the general software development process. > The best way is to show how you don't fall into the same issue any longer, Your expectations go into lower failure probabilities. But you might become disappointed again because of human work in general. > and it essentially means the actual testing of the patches. I find that corresponding progress depends then also on reasonable and accepted procedures from trusted test environments. > Now it's clear why the testing is demanded? I can follow your desire to some degree. > There is no other way. There are more (technical) possibilities to consider where development tools like a continuous integration system can help. Regards, Markus