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: <20090414013948.GA30336@elte.hu>
Date:	Tue, 14 Apr 2009 03:39:48 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Michal Simek <michal.simek@...alogix.com>,
	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>,
	Peter Korsgaard <jacmet@...site.dk>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [GIT PULL, v3] Microblaze architecture (arch/microblaze/)
	support


* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> 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.

FYI, there's a patch queued up by Michal for this - see below. It's 
Tested-by Jeff as well. You might want to apply this from email if 
you want a distclean-correct -rc2 ?

	Ingo

----- Forwarded message from monstr@...str.eu -----

Date: Mon, 13 Apr 2009 20:56:57 +0200
From: monstr@...str.eu
To: jeff@...zik.org
Subject: [PATCH 1/1] microblaze: Fix problem with removing zero length files
Cc: mingo@...e.hu, linux-kernel@...r.kernel.org,
	Michal Simek <monstr@...str.eu>

From: Michal Simek <monstr@...str.eu>

Adding one new line was recommended solution.
Test with make distclean

Signed-off-by: Michal Simek <monstr@...str.eu>
---
 arch/microblaze/include/asm/auxvec.h   |    1 +
 arch/microblaze/include/asm/cputable.h |    1 +
 arch/microblaze/include/asm/hw_irq.h   |    1 +
 arch/microblaze/include/asm/user.h     |    1 +
 arch/microblaze/include/asm/vga.h      |    1 +
 5 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/arch/microblaze/include/asm/auxvec.h b/arch/microblaze/include/asm/auxvec.h
index e69de29..8b13789 100644
--- a/arch/microblaze/include/asm/auxvec.h
+++ b/arch/microblaze/include/asm/auxvec.h
@@ -0,0 +1 @@
+
diff --git a/arch/microblaze/include/asm/cputable.h b/arch/microblaze/include/asm/cputable.h
index e69de29..8b13789 100644
--- a/arch/microblaze/include/asm/cputable.h
+++ b/arch/microblaze/include/asm/cputable.h
@@ -0,0 +1 @@
+
diff --git a/arch/microblaze/include/asm/hw_irq.h b/arch/microblaze/include/asm/hw_irq.h
index e69de29..8b13789 100644
--- a/arch/microblaze/include/asm/hw_irq.h
+++ b/arch/microblaze/include/asm/hw_irq.h
@@ -0,0 +1 @@
+
diff --git a/arch/microblaze/include/asm/user.h b/arch/microblaze/include/asm/user.h
index e69de29..8b13789 100644
--- a/arch/microblaze/include/asm/user.h
+++ b/arch/microblaze/include/asm/user.h
@@ -0,0 +1 @@
+
diff --git a/arch/microblaze/include/asm/vga.h b/arch/microblaze/include/asm/vga.h
index e69de29..8b13789 100644
--- a/arch/microblaze/include/asm/vga.h
+++ b/arch/microblaze/include/asm/vga.h
@@ -0,0 +1 @@
+
-- 
1.5.5.1

----- End forwarded message -----
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ