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: <200804232301.46764.arnd@arndb.de>
Date:	Wed, 23 Apr 2008 23:01:45 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Florian Fainelli <florian.fainelli@...ecomint.eu>
Cc:	monstr@...nam.cz, Paul Mackerras <paulus@...ba.org>,
	benh@...nel.crashing.org,
	Stephen Neuendorffer <stephen.neuendorffer@...inx.com>,
	John Williams <john.williams@...alogix.com>,
	jwboyer@...ux.vnet.ibm.com, John Linn <John.Linn@...inx.com>,
	git-dev@...inx.com, Grant Likely <grant.likely@...retlab.ca>,
	git@...inx.com, microblaze-uclinux@...e.uq.edu.au,
	linux-kernel@...r.kernel.org
Subject: Re: Microblaze Linux release

On Wednesday 23 April 2008, Florian Fainelli wrote:
> While reading the previous discussion, I wondered that keeping PCI would be a 
> good idea. I am personnaly using it for a custom design and would be glad 
> being able to continue using it.
> 
> If this represents too much work for you, we can probably add it later.
> 

The problem as far as I can see is that the existing header files
just don't work without a platform implementation.

I think it would be less confusing to leave them out. If you 
need PCI, it's probably easier to add new files for these
and get them working at the same time.

	Arnd <><
--
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/