Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: Aaditya Rai <arai@atheros.com>
Cc: linux-mips@linux-mips.org
Subject: Re: mips 2.4 vs 2.6 stability.
Date: Fri, 21 Oct 2005 22:14:53 -0500	[thread overview]
Message-ID: <4359AEAD.8010604@realitydiluted.com> (raw)
In-Reply-To: <43598DFE.8040100@atheros.com>

Aaditya Rai wrote:
> Hi everyone, I've searched the list for an answer and gotten, "there's 
> no stable release; check out from cvs" ;-)
> I'm trying to figure out if there are stability issues with mips port of 
> 2.6? Specifically for 24K? Is mips-2.4 generally considered to be more 
> stable?
>
Use 2.6 if you are working with 24K. Yes, it is stable that's why we are
using 2.6 and not 2.5 because the even numbers are stable releases. *sigh*
Geesh, kids these days.

-Steve

  reply	other threads:[~2005-10-22  3:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-22  0:55 mips 2.4 vs 2.6 stability Aaditya Rai
2005-10-22  3:14 ` Steven J. Hill [this message]
2005-10-22 13:29   ` 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=4359AEAD.8010604@realitydiluted.com \
    --to=sjhill@realitydiluted.com \
    --cc=arai@atheros.com \
    --cc=linux-mips@linux-mips.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