Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Kumba <kumba@gentoo.org>
Cc: linux-mips@linux-mips.org
Subject: Re: linux 2.4 and Indy
Date: Sat, 31 Jan 2004 04:04:35 +0100	[thread overview]
Message-ID: <20040131030435.GA24228@linux-mips.org> (raw)
In-Reply-To: <4018E322.9030801@gentoo.org>

On Thu, Jan 29, 2004 at 05:40:34AM -0500, Kumba wrote:

> Check out a cvs tree no later than 12/11/2003, a change in CVS after 
> that date seems to have nuked r4k kernels.  It is believed the change in 
> question is:
> 
> http://www.linux-mips.org/archives/linux-cvs/2003-12/msg00031.html
> 
> I've not yet been able to find a 'clean' way to remove the changes to 
> those specific files in that commit while keeping all the changes made 
> afterwards intact to test this idea.

Over the past days a few fixes went into CVS, the last only a few minutes
ago.  Can you retry and let me know?

  Ralf

  parent reply	other threads:[~2004-01-31  3:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 10:22 linux 2.4 and Indy Jorik Jonker
2004-01-29 10:40 ` Kumba
2004-01-30 10:59   ` Jorik Jonker
2004-01-30 11:12     ` Dominik 'Rathann' Mierzejewski
2004-01-30 20:49       ` Jorik Jonker
2004-01-30 21:01         ` Jorik Jonker
2004-01-31  3:04   ` Ralf Baechle [this message]
2004-01-31 14:10     ` Jorik Jonker
2004-02-01  4:52       ` R4600 V1.7 errata Ralf Baechle
2004-02-03 11:39         ` Ralf Baechle
2004-02-03 11:42           ` Dominik 'Rathann' Mierzejewski
2004-02-03 11:52             ` Ralf Baechle
2004-02-03 15:43               ` Maciej W. Rozycki
2004-02-03 16:12                 ` Ralf Baechle
2004-02-03 16:20                   ` Maciej W. Rozycki
2004-02-04 15:48             ` Dominik 'Rathann' Mierzejewski
2004-02-04 15:59               ` Pete Popov
2004-02-04 20:04                 ` 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=20040131030435.GA24228@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=kumba@gentoo.org \
    --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