linux-kernel - Re: [GIT PULL, v3] Microblaze architecture (arch/microblaze/) support

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: <alpine.LFD.2.00.0904131818050.26713@localhost.localdomain>
Date:	Mon, 13 Apr 2009 18:19:38 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Michal Simek <michal.simek@...alogix.com>
cc:	Linux Kernel list <linux-kernel@...r.kernel.org>,
	lkml <linux-arch@...r.kernel.org>,
	microblaze-uclinux@...e.uq.edu.au, Arnd Bergmann <arnd@...db.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	John Williams <john.williams@...alogix.com>,
	John Linn <John.Linn@...inx.com>,
	Stephen Neuendorffer <stephenn@...inx.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Korsgaard <jacmet@...site.dk>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [GIT PULL, v3] Microblaze architecture (arch/microblaze/)
 support



On Wed, 8 Apr 2009, Michal Simek wrote:
> 
> This repository contains Linux support for Xilinx Microblaze CPU.
> 
> Please pull
>     git://git.monstr.eu/linux-2.6-microblaze.git for-linus

So I pulled, but I notice that there's a few empty header files.

That looks intentional (they came in through a commit that says "headers 
simple files - empty or redirect to asm-generic"), but it means that "make 
distclean" will remove them. So if you really want an empty header file, 
you should really make it not _completely_ empty - add a comment to it or 
something.

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