From: benh@kernel.crashing.org
To: Christopher Murtagh <christopher.murtagh@mcgill.ca>
Cc: <linuxppc-dev@lists.linuxppc.org>, <tech@totalimpact.com>
Subject: Re: 2.4 kernel on briQ
Date: Wed, 10 Apr 2002 16:24:12 +0100 [thread overview]
Message-ID: <20020410152413.13794@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0204100945320.25920-100000@blues.wcg.mcgill.ca>
>>I'm working on it. Though I don't have 1Gb of RAM, I expect it to work ;)
>>
>>Hopefully, by next week I will have something. I've been a bit too busy
>>lately to give it time.
>
> Awesome. Thanks Ben. I might be able to send/lend you the RAM if it would
>help at all. Let me know if it would.
Well, if you have problem with it once I release the kernel, then yes, I will
need the RAM.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-10 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 2:32 2.4 kernel on briQ Christopher Murtagh
2002-04-10 9:08 ` benh
2002-04-10 13:47 ` Christopher Murtagh
2002-04-10 15:24 ` benh [this message]
2002-05-18 17:53 ` 2.4 kernel on briQ - Available Karsten Jeppesen
2002-05-18 21:50 ` Christopher Murtagh
2002-05-18 17:56 ` Karsten Jeppesen
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=20020410152413.13794@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=christopher.murtagh@mcgill.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tech@totalimpact.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.