From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-next@vger.kernel.org, Mike Travis <travis@sgi.com>,
Yinghai Lu <yinghai@kernel.org>
Subject: linux-next: manual merge of the sparseirq tree with the cpus4096 tree
Date: Fri, 23 Jan 2009 16:09:58 +1100 [thread overview]
Message-ID: <20090123160958.0da33500.sfr@canb.auug.org.au> (raw)
Hi Ingo,
Today's linux-next merge of the sparseirq tree got a conflict in
kernel/irq/handle.c between commit
7f7ace0cda64c99599c23785f8979a072e118058 ("cpumask: update irq_desc to
use cpumask_var_t") from the cpus4096 tree and commit
d7e51e66899f95dabc89b4d4c6674a6e50fa37fc ("sparseirq: make some func to
be used with genirq") from the sparseirq tree.
I fixed it up (see below) and can carry the fix as necessary. I am not
sure if this needs something better.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
diff --cc kernel/irq/handle.c
index 375d68c,48299a8..0000000
--- a/kernel/irq/handle.c
+++ b/kernel/irq/handle.c
@@@ -236,8 -225,9 +237,10 @@@ int __init early_irq_init(void
for (i = 0; i < count; i++) {
desc[i].irq = i;
+ desc[i].kstat_irqs = kstat_irqs_all[i];
+ init_alloc_desc_masks(&desc[i], 0, true);
}
+
return arch_early_irq_init();
}
reply other threads:[~2009-01-23 5:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090123160958.0da33500.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=travis@sgi.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