From: Ralf Baechle <ralf@oss.sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: wesolows@foobazco.org (Keith M Wesolowski),
rjkm@convergence.de (Ralph Metzler),
jensenq@Lineo.COM (Quinn Jensen),
linux-mips@oss.sgi.com
Subject: Re: Linux on LSI EZ4102
Date: Fri, 20 Apr 2001 10:45:52 -0300 [thread overview]
Message-ID: <20010420104552.B1973@bacchus.dhis.org> (raw)
In-Reply-To: <E14pzEm-0005jl-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Apr 18, 2001 at 10:11:42PM +0100
On Wed, Apr 18, 2001 at 10:11:42PM +0100, Alan Cox wrote:
> > Any -ac kernel contains at most the same changes that are in the oss
> > tree. Trees other than the oss one, including ac, are likely to
> > contain more bugs.
>
> -ac has all the stuff Ralf has sent me. Linus has most of that. In some
> ways -ac has less bugs (eg the oss tree has serious disk corruption bugs -ac
> doesnt) but I certainly cant guarantee -ac will always build on mips, and
> right now with the sem changes it quite probably wont.
It won't nor will Linus latest pre-patch.
Time to start sending more patches to you & Linus ...
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@oss.sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Keith M Wesolowski <wesolows@foobazco.org>,
Ralph Metzler <rjkm@convergence.de>,
Quinn Jensen <jensenq@Lineo.COM>,
linux-mips@oss.sgi.com
Subject: Re: Linux on LSI EZ4102
Date: Fri, 20 Apr 2001 10:45:52 -0300 [thread overview]
Message-ID: <20010420104552.B1973@bacchus.dhis.org> (raw)
Message-ID: <20010420134552.O2d5CA5IBouwTrMAw0wpDCywC48crXJ-YJTL6pKSsXg@z> (raw)
In-Reply-To: <E14pzEm-0005jl-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Apr 18, 2001 at 10:11:42PM +0100
On Wed, Apr 18, 2001 at 10:11:42PM +0100, Alan Cox wrote:
> > Any -ac kernel contains at most the same changes that are in the oss
> > tree. Trees other than the oss one, including ac, are likely to
> > contain more bugs.
>
> -ac has all the stuff Ralf has sent me. Linus has most of that. In some
> ways -ac has less bugs (eg the oss tree has serious disk corruption bugs -ac
> doesnt) but I certainly cant guarantee -ac will always build on mips, and
> right now with the sem changes it quite probably wont.
It won't nor will Linus latest pre-patch.
Time to start sending more patches to you & Linus ...
Ralf
next prev parent reply other threads:[~2001-04-20 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 0:08 Linux on LSI EZ4102 Ralph Metzler
2001-04-18 16:24 ` Quinn Jensen
2001-04-18 19:02 ` Ralph Metzler
2001-04-18 20:23 ` Keith M Wesolowski
2001-04-18 21:11 ` Alan Cox
2001-04-18 21:11 ` Alan Cox
2001-04-20 13:45 ` Ralf Baechle [this message]
2001-04-20 13:45 ` Ralf Baechle
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=20010420104552.B1973@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jensenq@Lineo.COM \
--cc=linux-mips@oss.sgi.com \
--cc=rjkm@convergence.de \
--cc=wesolows@foobazco.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