From: David Miller <davem@davemloft.net>
To: yinghai@kernel.org
Cc: mpm@selenic.com, mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: sparc64 build breakage...
Date: Wed, 21 Jan 2009 17:18:49 -0800 (PST) [thread overview]
Message-ID: <20090121.171849.220592075.davem@davemloft.net> (raw)
In-Reply-To: <20090121.171553.142827920.davem@davemloft.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: Text/Plain; charset=utf-8, Size: 1222 bytes --]
From: David Miller <davem@davemloft.net>
Date: Wed, 21 Jan 2009 17:15:53 -0800 (PST)
>
> This change:
>
> commit d7e51e66899f95dabc89b4d4c6674a6e50fa37fc
> Author: Yinghai Lu <yinghai@kernel.org>
> Date: Wed Jan 7 15:03:13 2009 -0800
>
> sparseirq: make some func to be used with genirq
>
> breaks the sparc64 build:
...
> arch/sparc/kernel/irq_64.c: In function âshow_interruptsâ:
> arch/sparc/kernel/irq_64.c:188: error: âstruct kernel_statâ has no member named âirqsâ
> make[1]: *** [arch/sparc/kernel/irq_64.o] Error 1
>
> This should fix it:
>
> sparc64: Fix build by using kstat_irqs_cpu().
Actually this isn't enough, next failure:
arch/sparc/kernel/time_64.c: In function âtimer_interruptâ:
arch/sparc/kernel/time_64.c:732: error: implicit declaration of function âkstat_incr_irqs_this_cpuâ
make[1]: *** [arch/sparc/kernel/time_64.o] Error 1
There seems to be a disconnect in linux/kernel_stat.h about
providing the same set of interfaces whether GENERIC_IRQS
is set or not. kstat_incr_irqs_this_cpu is one example.
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2009-01-22 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 1:15 David Miller
2009-01-22 1:18 ` David Miller [this message]
2009-01-22 1:24 ` David Miller
2009-01-22 8:11 ` Ingo Molnar
2009-01-22 8:38 ` Yinghai Lu
2009-01-22 9:20 ` Ingo Molnar
2009-01-22 2:34 ` Yinghai Lu
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=20090121.171849.220592075.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=yinghai@kernel.org \
/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
all inboxes | Powered by JetHome®