From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752638AbdK1NRu (ORCPT ); Tue, 28 Nov 2017 08:17:50 -0500 Received: from mout.web.de ([212.227.15.4]:59613 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752215AbdK1NRs (ORCPT ); Tue, 28 Nov 2017 08:17:48 -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> From: SF Markus Elfring Message-ID: <9a9348f4-d059-de28-1445-0189b7fb0ba3@users.sourceforge.net> Date: Tue, 28 Nov 2017 14:17:00 +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:fBY1yjSz9tRowsi/qzaqf8XcbUI9akf7AphBIKyLcjohKUjHf2B woxshi+x1otOsmopXJoplFUypNzpzhFiioV4eE/WqVVXJLgJ6tQ5Xl9hpv5EvveNYB2P2Hl PAkDFSAjmW7Pc7usebrqRwknFxIZPbk7fdwJH8CF+vzTx19PdJmRgLshDtPkRo6L6hOHV8s kLGz6W3smroq6iN0zEToQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:PjFDJdv8WbM=:OmNow5zekqugecSi1Jk9KF i7YZruASrE/mpvcoeyqBDO6+scPbW8LMjRDlY5r2ENvpV21dETSpCwqCeYQt7ruPZkbySN/Lr PY3XIVy6q7oUSFELOj2R13DyywGLym3UJ9h5UeoJT9aZ7ZsnwUqyjgZsRzkFI5lmlO/D+7cs2 6+thxjnQWp9ueosKAu1gWk/BtZ55lDDf/x4Pj7U5fVxjIvneqIm3MTfGoXchOZ3OzeKm/PFWO HIHHa4Zc3m+vBk1JAjYYMruGfIEp86kSSXf9p81wYw0VSuS7KYGdLtd7SnwI6OgKWMoZ0c2o8 O6M/xJl5kw7Mm+a8mn+RV7Z7pjiDg4zyqLCL3ab0Cwm7ob/kJdaNRdHFQ1raIBoe6z6cJEIaj ws2/484KiBIDq70wMKsTVmtCVgPufs/vX3vOOz45enhLkbu6J5k+vCsW2QadJhM7+3r+L7u1F hm0VwlGeHb1amaO/rOIwEGLLeBs9rUTNsT+az9WDor32cnQEcmGWyqMw02Cpt5nRUxzOQ+xqB NOc0p2+qZc8+BBEQNYcn8oHaFN241JlGwZpZ+RLpFqV8MLf2oTxs9heXNbwFlpNGI9yTqbP99 sKi7TQJzsr+Q+jzYYyO4114Fi9Tz5guCraaXdH0I5ghOlj0vWNv9nxdVkfrMCNsLfgtJG/TkS a8pmfgGLTtW8x9OiOlEG2No4ABsP+tOLz2nRg4vY2gmEFUK9Ygz/Yi/S/NIWRnJFqlNIqA82W DDsnnSnPP3Zsl+utU+nfBtc4ZX71/MRDhrCuEdoRmR6S1+2N8X5NvSmE/rnVv3TswvVXt4zqk UjrvOaeSVrBNRVn3+K8Hn5AUM5ZQ4S4TvlN+fCNw54YqzZFdj0= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> Which test results would you like to see or hear (!) from a real device >> (or a configuration in a virtual machine)? > > I don't mind either case as long as the test works. How would you notice that a corresponding system test worked in reasonable ways? >> I find such a development tool very relevant to reduce your concerns. > > It's about your patches, not my system. Your own automatic test system could provide a bit of more confidence for some change possibilities, couldn't it? Regards, Markus