From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Dave Jones <davej@codemonkey.org.uk>,
James Simmons <jsimmons@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
dank@reflexsecurity.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test1-ac1 Matrox Compile Error
Date: Tue, 15 Jul 2003 22:00:48 +0200 [thread overview]
Message-ID: <20030715200048.GF8240@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20030715193224.GE20424@suse.de>
On Tue, 15 July 2003 20:32:24 +0100, Dave Jones wrote:
> On Tue, Jul 15, 2003 at 09:28:53PM +0200, J?rn Engel wrote:
>
> > So what is lunatic about doing the same with 2.6test?
>
> Simple, there are known problems in 2.6.0test.
> At the time of embedded folks using 2.4.5, there were no known problems.
The VM was enough of a problem for one flamewar or another. There is
even a faint memory of major construction work around 2.4.10.
You may be right for an x86 design that work out of the box, but I got
used to extensive adjustments and just as extensive test afterwards.
If those test are successful, the kernel is stable by definition,
whatever the known problems may be.
Jörn
--
Eighty percent of success is showing up.
-- Woody Allen
next prev parent reply other threads:[~2003-07-15 19:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 16:03 2.6.0-test1-ac1 Matrox Compile Error Adam Voigt
2003-07-15 16:16 ` nick black
2003-07-15 16:40 ` James Simmons
2003-07-15 17:13 ` Dave Jones
2003-07-15 17:30 ` Alan Cox
2003-07-15 17:43 ` James Simmons
2003-07-15 17:49 ` Alan Cox
2003-07-15 18:36 ` James Simmons
2003-07-15 17:57 ` Dave Jones
2003-07-15 18:49 ` Jörn Engel
2003-07-15 19:13 ` Dave Jones
2003-07-15 19:28 ` Jörn Engel
2003-07-15 19:32 ` Dave Jones
2003-07-15 20:00 ` Jörn Engel [this message]
2003-07-17 17:03 ` James Simmons
2003-07-17 17:07 ` Dave Jones
2003-07-17 17:37 ` James Simmons
2003-07-15 17:02 ` Adam Voigt
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=20030715200048.GF8240@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dank@reflexsecurity.com \
--cc=davej@codemonkey.org.uk \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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).