linux-kernel - RE: Microblaze Linux release

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080414155554.5B8CD98059@mail51-sin.bigfish.com>
Date:	Mon, 14 Apr 2008 08:55:52 -0700
From:	"Stephen Neuendorffer" <stephen.neuendorffer@...inx.com>
To:	<monstr@...nam.cz>, "Josh Boyer" <jwboyer@...ux.vnet.ibm.com>
Cc:	"John Williams" <john.williams@...alogix.com>,
	<benh@...nel.crashing.org>, "John Linn" <linnj@...inx.com>,
	"git-dev" <git-dev@...inx.com>,
	"Grant Likely" <grant.likely@...retlab.ca>,
	<microblaze-uclinux@...e.uq.edu.au>,
	<linux-kernel@...r.kernel.org>, <paulus@...ba.org>
Subject: RE: Microblaze Linux release



> -----Original Message-----
> From: Michal Simek [mailto:monstr@...nam.cz]
> Sent: Sunday, April 13, 2008 11:51 AM
> To: Josh Boyer
> Cc: Stephen Neuendorffer; John Williams; benh@...nel.crashing.org;
John Linn; git-dev; Grant Likely;
> git; microblaze-uclinux@...e.uq.edu.au; linux-kernel@...r.kernel.org;
paulus@...ba.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/