From: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
To: <monstr@seznam.cz>, "Josh Boyer" <jwboyer@linux.vnet.ibm.com>
Cc: "John Williams" <john.williams@petalogix.com>,
<benh@kernel.crashing.org>, "John Linn" <linnj@xilinx.com>,
"git-dev" <git-dev@xilinx.com>,
"Grant Likely" <grant.likely@secretlab.ca>,
<microblaze-uclinux@itee.uq.edu.au>,
<linux-kernel@vger.kernel.org>, <paulus@samba.org>
Subject: RE: Microblaze Linux release
Date: Mon, 14 Apr 2008 08:55:52 -0700 [thread overview]
Message-ID: <20080414155554.5B8CD98059@mail51-sin.bigfish.com> (raw)
In-Reply-To: <4802560D.3020308@seznam.cz>
> -----Original Message-----
> From: Michal Simek [mailto:monstr@seznam.cz]
> Sent: Sunday, April 13, 2008 11:51 AM
> To: Josh Boyer
> Cc: Stephen Neuendorffer; John Williams; benh@kernel.crashing.org;
John Linn; git-dev; Grant Likely;
> git; microblaze-uclinux@itee.uq.edu.au; linux-kernel@vger.kernel.org;
paulus@samba.org
> Subject: Re: Microblaze Linux release
>
> Hi Josh,
>
> >> Hi Everybody,
> >>
> >> I fixed all reported bugs which I got from LKML and from you.
> >> Latest version of Microblaze Linux kernel is available at
git.monstr.eu.
> >> There is git repository called linux-microblaze.git
> >> Microblaze port is based on 2.6.24-rc5. I'll create the new repo
with clean pack
> >> of changes based on latest kernel version for easier pull.
> >>
> >> Merge windows will be open hopefully next week and I would like to
send pull
> >> request to Paul.
> >
> > Why Paul? If microblaze is a new architecture (which it seems to
be),
> > then you should really work through Linus directly.
>
> I don't know who start with it. For me is not this point important.
> I think that was Steve's idea, wasn't it?
Nope, it should go through Linus. My hope was to recruit reviewers from
the powerpc community, since there is alot of overlap (device trees,
drivers, the MMU is very similar).
Steve
next prev parent reply other threads:[~2008-04-14 15:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 13:26 Microblaze Linux release Michal Simek
2008-04-13 13:33 ` Grant Likely
2008-04-13 15:44 ` Michal Simek
2008-04-13 15:13 ` Josh Boyer
2008-04-13 18:50 ` Michal Simek
2008-04-14 15:55 ` Stephen Neuendorffer [this message]
2008-04-15 12:59 ` Michal Simek
2008-04-14 3:38 ` Arnd Bergmann
2008-04-14 5:10 ` H. Peter Anvin
2008-04-14 6:55 ` Arnd Bergmann
2008-04-14 6:01 ` Arnd Bergmann
2008-04-15 12:54 ` Michal Simek
2008-04-15 13:32 ` Arnd Bergmann
2008-04-15 21:52 ` Benjamin Herrenschmidt
2008-04-16 6:24 ` Michal Simek
2008-04-16 7:31 ` Paul Mackerras
2008-04-16 7:44 ` Arnd Bergmann
2008-04-16 15:28 ` Michal Simek
2008-04-16 15:33 ` Arnd Bergmann
2008-04-23 20:55 ` Michal Simek
2008-04-23 20:57 ` Florian Fainelli
2008-04-23 21:01 ` Arnd Bergmann
2008-04-23 21:08 ` Michal Simek
2008-04-23 21:22 ` Michal Simek
2008-04-23 22:51 ` John Williams
2008-04-16 15:26 ` Michal Simek
2008-04-16 7:45 ` Benjamin Herrenschmidt
2008-04-23 21:35 ` Michal Simek
2008-04-23 20:57 ` Michal Simek
2008-04-18 17:56 ` [microblaze-uclinux] " Stephen Neuendorffer
2008-04-19 10:38 ` Michal Simek
2008-04-14 7:10 ` Michal Simek
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=20080414155554.5B8CD98059@mail51-sin.bigfish.com \
--to=stephen.neuendorffer@xilinx.com \
--cc=benh@kernel.crashing.org \
--cc=git-dev@xilinx.com \
--cc=grant.likely@secretlab.ca \
--cc=john.williams@petalogix.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linnj@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@seznam.cz \
--cc=paulus@samba.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 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.