alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Cc: Arvind Yadav <arvind.yadav.cs@gmail.com>,
	Takashi Sakamoto <o-takashi@sakamocchi.jp>,
	kernel-janitors@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: ALSA: nm256: Fine-tuning for three function implementations
Date: Tue, 28 Nov 2017 21:18:01 +0100	[thread overview]
Message-ID: <ed8d5cd3-ae6e-db9e-fa55-fe5842102a51@users.sourceforge.net> (raw)
In-Reply-To: <s5hbmjmjhr1.wl-tiwai@suse.de>

>> 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

  reply	other threads:[~2017-11-28 20:18 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 17:05 [PATCH 0/2] ALSA: nm256: Fine-tuning for three function implementations SF Markus Elfring
2017-11-16 17:07 ` [PATCH 1/2] ALSA: nm256: Adjust five function calls together with a variable assignment SF Markus Elfring
2017-11-16 17:08 ` [PATCH 2/2] ALSA: nm256: Use common error handling code in snd_nm256_probe() SF Markus Elfring
2017-11-16 17:15 ` [PATCH 0/2] ALSA: nm256: Fine-tuning for three function implementations Takashi Iwai
2017-11-16 17:48   ` SF Markus Elfring
2017-11-16 18:54     ` Takashi Iwai
2017-11-16 19:30       ` SF Markus Elfring
2017-11-28  7:46         ` Takashi Iwai
2017-11-28  8:19           ` SF Markus Elfring
2017-11-28  9:10             ` Takashi Iwai
2017-11-28  9:50               ` SF Markus Elfring
2017-11-28 11:37                 ` Takashi Iwai
2017-11-28 12:33                   ` SF Markus Elfring
2017-11-28 12:46                     ` Takashi Iwai
2017-11-28 13:00                       ` SF Markus Elfring
2017-11-28 13:06                         ` Takashi Iwai
2017-11-28 13:17                           ` SF Markus Elfring
2017-11-28 13:38                             ` Takashi Iwai
2017-11-28 14:19                               ` SF Markus Elfring
2017-11-28 14:27                                 ` Takashi Iwai
2017-11-28 14:33                                   ` SF Markus Elfring
2017-11-28 14:38                                     ` Takashi Iwai
2017-11-28 14:44                                       ` SF Markus Elfring
2017-11-28 14:53                                         ` Takashi Iwai
2017-11-28 15:01                                           ` SF Markus Elfring
2017-11-28 15:21                                             ` Takashi Iwai
2017-11-28 16:15                                               ` SF Markus Elfring
2017-11-28 16:27                                                 ` Takashi Iwai
2017-11-28 16:40                                                   ` SF Markus Elfring
2017-11-28 16:44                                                     ` Takashi Iwai
2017-11-28 17:15                                                       ` SF Markus Elfring
2017-11-28 18:35                                                         ` Takashi Iwai
2017-11-28 19:08                                                           ` SF Markus Elfring
2017-11-28 19:43                                                             ` Takashi Iwai
2017-11-28 19:48                                                               ` SF Markus Elfring
2017-11-28 19:54                                                                 ` Takashi Iwai
2017-11-28 19:57                                                                   ` SF Markus Elfring
2017-11-28 20:00                                                                     ` Takashi Iwai
2017-11-28 20:18                                                                       ` SF Markus Elfring [this message]
2017-11-28 20:25                                                                         ` Takashi Iwai
2017-11-28 20:32                                                                           ` SF Markus Elfring
2017-11-29 10:34               ` SF Markus Elfring
2017-11-28 12:33             ` [alsa-devel] " Ondrej Zary
2017-11-28 13:10               ` SF Markus Elfring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ed8d5cd3-ae6e-db9e-fa55-fe5842102a51@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=arvind.yadav.cs@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=o-takashi@sakamocchi.jp \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).