From: Shane Nay <shane@minirl.com>
To: James Simmons <jsimmons@transvirtual.com>, Pavel Machek <pavel@suse.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mips@oss.sgi.com, linux-mips-kernel@lists.sourceforge.net
Subject: Re: [ANNOUNCE] Secondary mips tree.
Date: Mon, 16 Jul 2001 03:22:40 -0700 [thread overview]
Message-ID: <0107160322400A.02677@compiler> (raw)
In-Reply-To: <Pine.LNX.4.10.10107130800230.30223-100000@transvirtual.com>
In-Reply-To: <Pine.LNX.4.10.10107130800230.30223-100000@transvirtual.com>
On Friday 13 July 2001 08:01, James Simmons wrote:
> > Good. I should definitely take a look. [Do you care about vr4130 or about
> > tx3912, too?]
>
> Yes. If you want to work on it no problem.
Huh, Very Cool. I was getting ready to queue up a huge IRDA forward port in
linux-vr to the 2.4.6 version. (Still el-crashola on me right now) The one
in the present repository likes to overwrite userspace applications pretty
much at randomn.
Maybe after things simmer down I'll port the Agenda hardware platform over to
your repository, and Agenda can switch to using that. linux-vr has been
really really stale since we froze at our present version for toolchain
reasons. Those toolchain problems were fixed ages ago, but Mike & Brad who
had been responsible for forward porting the kernel stopped doing that work
for the most part.
Thanks,
Shane Nay.
next prev parent reply other threads:[~2001-07-16 10:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 20:57 [ANNOUNCE] Secondary mips tree James Simmons
2001-06-30 14:57 ` Pavel Machek
2001-07-08 18:32 ` James Simmons
2001-07-09 12:02 ` Pavel Machek
2001-07-12 21:47 ` strange 2.4.x problems with dual machine ognen
2001-07-13 15:01 ` [ANNOUNCE] Secondary mips tree James Simmons
2001-07-16 10:22 ` Shane Nay [this message]
2001-07-16 19:27 ` [Linux-mips-kernel] " James Simmons
2001-07-17 7:16 ` Shane Nay
2001-07-17 15:35 ` H . J . Lu
2001-07-17 16:41 ` Toolchains James Simmons
2001-07-17 17:20 ` Toolchains H . J . Lu
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=0107160322400A.02677@compiler \
--to=shane@minirl.com \
--cc=jsimmons@transvirtual.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips-kernel@lists.sourceforge.net \
--cc=linux-mips@oss.sgi.com \
--cc=pavel@suse.cz \
/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