linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Gerhard Jaeger <g.jaeger@sysgo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [BUG] IBM440GX works too slow under nfsroot
Date: Sun, 7 Nov 2004 18:55:04 -0800	[thread overview]
Message-ID: <20041108025504.GA4112@gate.ebshome.net> (raw)
In-Reply-To: <200410250847.00907.g.jaeger@sysgo.com>

On Mon, Oct 25, 2004 at 08:47:00AM +0200, Gerhard Jaeger wrote:
> > If there is an interest, I can make a patch against current 2.4 BK
> > tree, but this will take some time (I'm a little swamped right now).
> 
> of course there's some interest, at least by me ;) Would be great if you'll
> find some time for that.

Patch against current 2.4 BK is available at http://kernel.ebshome.net. 
Quick tested on Ebony & Ocotea.

--
Eugene

  parent reply	other threads:[~2004-11-08  2:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21 23:57 [BUG] IBM440GX works too slow under nfsroot Hiroshi DOYU
2004-10-22  1:19 ` Eugene Surovegin
2004-10-22  1:26   ` Hiroshi DOYU
2004-10-22  1:33 ` Eugene Surovegin
2004-10-22  1:38   ` Hiroshi DOYU
2004-10-22  2:02     ` Eugene Surovegin
2004-10-22  6:26       ` Gerhard Jaeger
2004-10-22  8:29         ` Eugene Surovegin
2004-10-22  9:39           ` Gerhard Jaeger
2004-10-22 12:22           ` Mark Chambers
2004-10-22 12:27             ` Gerhard Jaeger
2004-10-25  1:16           ` Eugene Surovegin
2004-10-25  6:47             ` Gerhard Jaeger
2004-10-25  7:02               ` Eugene Surovegin
2004-11-08  2:55               ` Eugene Surovegin [this message]
2004-10-22 22:22     ` Matt Porter
  -- strict thread matches above, loose matches on Subject: below --
2004-10-22  5:57 Daren Hayward
2004-10-22  6:30 ` Gerhard Jaeger
2004-10-22  7:36 Neil Wilson

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=20041108025504.GA4112@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=g.jaeger@sysgo.com \
    --cc=linuxppc-embedded@ozlabs.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).