public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Pavel Machek <pavel@suse.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mips@oss.sgi.com
Subject: Re: [ANNOUNCE] Secondary mips tree.
Date: Mon, 9 Jul 2001 12:02:44 +0000	[thread overview]
Message-ID: <20010709120243.A39@toy.ucw.cz> (raw)
In-Reply-To: <20010630145732.E255@toy.ucw.cz> <Pine.LNX.4.10.10107081059580.22673-100000@transvirtual.com>
In-Reply-To: <Pine.LNX.4.10.10107081059580.22673-100000@transvirtual.com>; from jsimmons@transvirtual.com on Sun, Jul 08, 2001 at 11:32:31AM -0700

Hi!

> > >  	We have started a secondary tree for linux mips. This tree will
> > > be to SGI mips tree as Alan Cox's tree is to linus branch. We will test
> > > and play with "experimental patches" and then in time hand them off to the
> > > main branch Ralf Baechle maintains. Also one of the main reasons for this
> > > branch was to unite several of the mips trees into one place. Anyones
> > > patches (if good) are welcomed. The site is 
> > 
> > Do you want to "eat" linux-vr tree? linux-vr list is dead and there's no
> > (or not much) development in its CVS (at 240t7 :-()
> 
> Yes. We are reworking the VR code and placing it into our tree. 

Good. I should definitely take a look. [Do you care about vr4130 or about
tx3912, too?]

> > > We also have a mailing list which instructions are on the SF page on how
> > > to join. Thank you. 
> > 
> > Is it ok to be used as linux-vr list?
> 
> I have no problem with it. VR is apart of the mips developement we are
> doing. Also we do alot of IT 8172 and au1000 devleopement as well. Plus
> some early work for the cobalt cube is being done. I will finish the cube 
> now that we have a pretty generic pci code layer that is shared amoung
> many boards.

Seems like there's one more mailinglist for me to read. Ook.
								Pavel
-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.


  reply	other threads:[~2001-07-12 21:04 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 [this message]
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
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=20010709120243.A39@toy.ucw.cz \
    --to=pavel@suse.cz \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox