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 S1752626AbdK1OVH (ORCPT <rfc822;w@1wt.eu>);
        Tue, 28 Nov 2017 09:21:07 -0500
Received: from mout.web.de ([212.227.15.4]:55484 "EHLO mout.web.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752112AbdK1OUs (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 28 Nov 2017 09:20:48 -0500
Subject: Re: ALSA: nm256: Fine-tuning for three function implementations
To: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Cc: Arvind Yadav <arvind.yadav.cs@gmail.com>,
        Jaroslav Kysela <perex@perex.cz>,
        Takashi Sakamoto <o-takashi@sakamocchi.jp>,
        kernel-janitors@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
References: <d98a2685-ddf9-1cba-839a-d12c5ff8d3ba@users.sourceforge.net>
 <s5hefoy16xg.wl-tiwai@suse.de>
 <dfa99045-f213-3dad-b1f4-2e90eb38ddbd@users.sourceforge.net>
 <s5h7euq9hqt.wl-tiwai@suse.de>
 <24f8c777-1eb4-e7e7-9371-79f32700c9dc@users.sourceforge.net>
 <s5hbmjmluba.wl-tiwai@suse.de>
 <2cbef557-5f89-c630-e108-14ef2ce6b41a@users.sourceforge.net>
 <s5h4lpelqfm.wl-tiwai@suse.de>
 <1547a4c2-5b70-e3a3-b482-d28c538e615c@users.sourceforge.net>
 <s5hy3mqr5v9.wl-tiwai@suse.de>
 <c2b7543c-cd2c-f7f6-98f3-23e2ca6f8b90@users.sourceforge.net>
 <s5hshcyr2on.wl-tiwai@suse.de>
 <539adde3-a713-721f-2a0d-1d1ef925fb86@users.sourceforge.net>
 <s5hpo82r1s5.wl-tiwai@suse.de>
 <9a9348f4-d059-de28-1445-0189b7fb0ba3@users.sourceforge.net>
 <s5hlgiqr0ad.wl-tiwai@suse.de>
From: SF Markus Elfring <elfring@users.sourceforge.net>
Message-ID: <3b7b24bd-4bdf-752e-1a62-cc71e9152acc@users.sourceforge.net>
Date: Tue, 28 Nov 2017 15:19:55 +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: <s5hlgiqr0ad.wl-tiwai@suse.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:ZnwclvdBgT2iyNJoMnwMZDWSlBeR9Myy/BeiJ9phsfZagstv361
 Y89iZQRpUqew6zJBj23Yzwz8BFaBgHGmIjAd9UeV5BPabldRoIkxt407aELNhFpAxELORpv
 +ppgprFq/UZWptUviUQJOx1O90ZXB7BaPy3L2D+4Oeeu2VQRvoRtmiWsEHYfXFjhvDPaobZ
 Xqq15lQb+3ewHDVroK/xQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:jC5ycsE67KQ=:2EMD13lAfbMky4s6RwzVI8
 Ma1dpyR5YisJjpmHDRbCckFmvL++ATrbeHn7PV4Z0EA5nxbc2EDokfBdfOd+4GqieqDDNcga9
 Iy6fOQUz9aCSQgsbfU5rFpNKP8HU6YQOYMUJ0+kmPknPAAR+LC9hDJ7HWmFyNhJMWLC3x7TOn
 8S47B4nQzr1jQRIRl29X5jri5lOiLAQ+CIX36uHT9tNduavRx1B9C1Ut2r7GsmCfr7vSFnA8y
 +GicuXYV0rHeaMNgwcB3LKMEjOFy5HUNyjboUSSfd4P8YZ22bnILN0BzxXnIT9Bs7rtOGQeIE
 TQ1/T5pUzAptM5hXFRytbFKWkF6diEz8u0a2hde3WQ74e9fiRkH5abgPPKtnF4zP4ggW0OehX
 Eb2UrQjpmsq6BMkFQ5QOSJu9/t4KhbwAAjTMGs4dJHt8LSr3fKf3lriRcOpkAq3qoFmjWvO9C
 PMcUU34fkSCYjPeMI6N7JRNyn3ccHhb00fVsV8adVE7iGqeO8nYkL4/zsVKhKZIlqPBD/eeXR
 f0R7Mp15WkNUEo8IOpjVLGI/jfL4C5uOVsqQarXj3RCwMT5B/ccdYLBwViGnBL8gpuZv0FjTW
 j/7Pk+r184wtVY4v19RcBNLhneuBarua56jTfFQ2bnC6UcFj90c/WeKHxftvzOvAyEqAPo4mG
 VrtizTLrpx/LBDiHpuuShGzFqIwMYS7EQVlxHlQsZFdRKLYLDHuZNMeFHZWIg9atxqkkRuPEF
 9eOnpKkXYarqOCxa8qUYmKiuyXf0jqPCehwG+FdyngXY+PBPh6JhLx+T+AnSkHj4u7e8MOfnK
 rPkNfu1V7X80FO+ErR4o/WcjGPks5oTi6jsc8ZnTA9T0gaGXqs=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

>> How would you notice that a corresponding system test worked
>> in reasonable ways?
> 
> It needs a trust to the patch author or the tester who reported that
> it worked.

Can this aspect vary over time?


> The test result should be mentioned concisely.

How do you think about to introduce accepted automatic test procedures?


> You shouldn't rely on my system.

Did this system get sufficient trust so far?


> The main point is your patch itself; make your patch more reliable.

It seems that I can make my adjustments only a bit more interesting
by positive review comments from other contributors
(if you can not become convinced by the concrete source code changes).

Regards,
Markus