From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Feb 18
Date: Mon, 18 Feb 2008 00:47:59 -0800 (PST) [thread overview]
Message-ID: <20080218.004759.27101677.davem@davemloft.net> (raw)
In-Reply-To: <20080218190841.eeed735f.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.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@davemloft.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) \
next prev parent reply other threads:[~2008-02-18 8:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 8:08 Stephen Rothwell
2008-02-18 8:14 ` Avi Kivity
2008-02-18 8:34 ` Stephen Rothwell
2008-02-18 8:47 ` David Miller [this message]
2008-02-18 23:56 ` Bartlomiej Zolnierkiewicz
2013-02-18 6:16 Stephen Rothwell
2014-02-18 5:06 Stephen Rothwell
2015-02-18 3:22 Stephen Rothwell
2016-02-18 7:31 Stephen Rothwell
2019-02-18 7:36 Stephen Rothwell
2020-02-18 4:28 Stephen Rothwell
2021-02-18 9:54 Stephen Rothwell
2025-02-18 5:15 Stephen Rothwell
2026-02-18 13:24 Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080218.004759.27101677.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome