From: Andi Kleen <ak@suse.de>
To: Mark Gross <mgross@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why is 2.6.12.2 less stable on my laptop than 2.6.10?
Date: 15 Jul 2005 02:38:58 +0200 [thread overview]
Message-ID: <p73wtnsx5r1.fsf@bragg.suse.de> (raw)
In-Reply-To: <200507140912.22532.mgross@linux.intel.com.suse.lists.linux.kernel>
Mark Gross <mgross@linux.intel.com> writes:
>
> The problem is the process, not than the code.
> * The issues are too much ad-hock code flux without enough disciplined/formal
> regression testing and review.
It's basically impossible to regression test swsusp except to release it.
Its success or failure depends on exactly the driver combination/platform/BIOS
version etc. e.g. all drivers have to cooperate and the particular
bugs in your BIOS need to be worked around etc. Since that is quite fragile
regressions are common.
However in some other cases I agree some more regression testing
before release would be nice. But that's not how Linux works. Linux
does regression testing after release.
-Andi
next parent reply other threads:[~2005-07-15 0:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200507140912.22532.mgross@linux.intel.com.suse.lists.linux.kernel>
2005-07-15 0:38 ` Andi Kleen [this message]
2005-07-15 1:45 ` Why is 2.6.12.2 less stable on my laptop than 2.6.10? Jesper Juhl
2005-07-15 2:02 ` Chris Friesen
2005-07-15 2:06 ` Jesper Juhl
2005-07-15 2:09 ` Andi Kleen
2005-07-15 21:33 ` Mark Gross
2005-07-15 2:16 ` Dave Airlie
2005-07-15 21:39 ` Mark Gross
2005-07-15 2:09 ` Dave Jones
2005-07-15 21:47 ` Mark Gross
2005-07-15 22:19 ` Dave Jones
2005-07-15 22:25 ` David Lang
2005-07-15 23:14 ` Rik van Riel
2005-07-18 21:14 ` Mark Gross
2005-07-19 10:12 ` Paolo Ciarrocchi
2005-07-15 2:09 ` Parag Warudkar
2005-07-15 2:14 ` Andi Kleen
2005-07-15 13:32 ` Alan Cox
2005-07-14 16:12 Mark Gross
2005-07-14 23:55 ` Andrew Morton
2005-07-15 8:45 ` Pavel Machek
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=p73wtnsx5r1.fsf@bragg.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
/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