linux-kernel - Re: linux-next: Tree for Feb 18

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 18 Feb 2008 00:47:59 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	sfr@...b.auug.org.au
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: Tree for Feb 18

From: Stephen Rothwell <sfr@...b.auug.org.au>
Date: Mon, 18 Feb 2008 19:08:41 +1100

> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.

The patch below fixes the allmodconfig build on sparc64
for me.

I notice on the build status page that sparc64 allmodconfig
fails in the CODA filesystem bits.  I suspect this is some
cross-build issue, and even moreso it appears the "u_quad"
definition is to blame and the way that gets defined in the
CODA fs headers is beyond questionable :-/

Anyways, here is the build fix:

[SPARC64]: Add ide_default_irq() implementation.

Signed-off-by: David S. Miller <davem@...emloft.net>

diff --git a/include/asm-sparc64/ide.h b/include/asm-sparc64/ide.h
index c5fdabe..5bfb064 100644
--- a/include/asm-sparc64/ide.h
+++ b/include/asm-sparc64/ide.h
@@ -24,6 +24,11 @@
 # endif
 #endif

+static inline int ide_default_irq(unsigned long base)
+{
+	return 0;
+}
+
 #define __ide_insl(data_reg, buffer, wcount) \
 	__ide_insw(data_reg, buffer, (wcount)<<1)
 #define __ide_outsl(data_reg, buffer, wcount) \
--
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/