From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Date: Tue, 28 Nov 2017 13:38:18 +0000 Subject: Re: ALSA: nm256: Fine-tuning for three function implementations Message-Id: List-Id: 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> In-Reply-To: <9a9348f4-d059-de28-1445-0189b7fb0ba3@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: SF Markus Elfring Cc: alsa-devel@alsa-project.org, Arvind Yadav , Jaroslav Kysela , Takashi Sakamoto , kernel-janitors@vger.kernel.org, LKML On Tue, 28 Nov 2017 14:17:00 +0100, SF Markus Elfring wrote: > > >> 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? It needs a trust to the patch author or the tester who reported that it worked. The test result should be mentioned concisely. > >> 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? You shouldn't rely on my system. The main point is your patch itself; make your patch more reliable. Takashi