linux-kernel - Re: [microblaze-uclinux] Re: microblaze syscall list

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]

Date:	Fri, 25 Apr 2008 04:06:14 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	John Williams <jwilliams@...e.uq.edu.au>
Cc:	microblaze-uclinux@...e.uq.edu.au, Arnd Bergmann <arnd@...db.de>,
	Will Newton <will.newton@...il.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	linux-arch@...r.kernel.org, git@...inx.com
Subject: Re: [microblaze-uclinux] Re: microblaze syscall list

On Fri, Apr 25, 2008 at 07:36:35PM +1000, John Williams wrote:
> Please remember that MicroBlaze has been around as an arch for > 4 
> years, just not in the kernel.org tree.  These older style syscall 
> interfaces are all part of the uClibc and glibc ports for MicroBlaze.

So is it fair to say that you now understand this was the Wrong Way To
Do Things, and if anyone asks, you'd recommend getting an arch merged
into kernel.org sooner rather than later?

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/