From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753864AbdK1QQO (ORCPT ); Tue, 28 Nov 2017 11:16:14 -0500 Received: from mout.web.de ([212.227.15.3]:49735 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752104AbdK1QQM (ORCPT ); Tue, 28 Nov 2017 11:16:12 -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> <539adde3-a713-721f-2a0d-1d1ef925fb86@users.sourceforge.net> <9a9348f4-d059-de28-1445-0189b7fb0ba3@users.sourceforge.net> <3b7b24bd-4bdf-752e-1a62-cc71e9152acc@users.sourceforge.net> From: SF Markus Elfring Message-ID: <6da7e6dc-b181-d26c-9f09-6592469193be@users.sourceforge.net> Date: Tue, 28 Nov 2017 17:15:27 +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:8xWZPRHbjQwF3tVe8EtthOmiVzQbwO4QLQ0GPheDA9UOAkvT+aI VHF7gFde20+ifdDa/2dm4etUXINL0XSoye5iNFGqv1grp3Fd2hrvF8ZsZrDRUd8Mkgx05Iu dfoTn5/VECT0o6jCk4LW7tJSJPwyGMqgQNShFScLiZrd6W9g0fU3WxWBbfhydCt9RG40AHa bnG73Flwf3SJNmnTR18zA== X-UI-Out-Filterresults: notjunk:1;V01:K0:jMr7TXFq6FA=:GGczwzC2aQIbUAgwfKKNtw ZhWY6dVcdyNLZ9jr4RPmTUqxTuGgvB8JQba+LfenpOQePlThTRluDZmUegorLtOSSybQzgZgC KALD2piHfzj2RkRREDsyyLDqJnwo9Oip8zxRe5yVq4ObYQgF8+Nj5bY69h2r4686NKrIpyM+h zFk8D5r6xxM6IdJb0K/vAJVuC3jKpA2ASPalOxOWMS/jrJz8zFNBqq2udRkxjTiIUX1SKEgiw 88jediUq4eXHJNj292JWLk4E4SsibVCMg2Qp9e7uxp5AfELpEFqlpJX5dm8IdliapbaR8Tumd W+scyWMe0dNIdyaPxMrn+UDDCGRoCOzLZURX8WLiyYXXhZtXB+AhVRX5bFN8X9KJMnaQdEZT/ 8Xqotr16RjVEBlfeUXj/kqsKSHlo7sQwtKLhFShMSPY0gqw6VJgQFqaeJwcJsDdNSyENFpSNP jkT6868cQD9Xa4BQ4aAJhpwIWthqAKcc5DTEuqOhSqwLYJ6R4tFzRBJ07VD5UklGC4cx4UzUy TWNam76pJHf1qdkj16FNTzi8OP7vGzeqfkGJuAgvDV17kMLJLBq+KlI3ZCAPHuDY0JwkERO9b pZEbIu3XOBpjzv2amAwUGMvGmGPmDWTZ23ZnXwyzcDXo1z8Zc/8rrGfQhCHnK7z+QqstWoLfL soYlECLJzc14ne6uFVdXJXh9G/v4Pnl+at0kqmlVb0hCL9up4Mfmb0GBcRSNxIgXUlRRt5BIO Zi1q9XFH9FZg4ObA4Z2+t67v43Natlj/PfFZJVpEBxVH7nLNeW/pJ2sI8N7xluOb/ZLjk/mlB 9d3Xx2gDMR5Mlbte3r4iT1W6i1ZZFDEWiMS3cZ4SHEdzxuDRQk= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Because I didn't see any test result from you, This is correct so far. > so I can't trust you. This view did not hinder you to integrate some of my update suggestions which you found easier to handle. >> Which test configurations would you trust finally? > > Do test whatever like the users do. I find such an information too unsafe for an official acceptance test. >> How can such descriptions improve the trust situation? > > It's the first step. At least then I can see you did some test. > Currently nothing. zero. nada. I am unsure if acceptable test results will ever be published for this software module. > How can I trust it? * Would you dare to inspect the shown source code adjustments again? * How do you think about to sort the remaining update candidates by their change size (or software age)? Regards, Markus