From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Ingo Molnar <mingo@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Andrew Morton <akpm@linux-foundation.org>,
Jack Steiner <steiner@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] irq: update all archs to use new irq_desc cpumask_var_t's.
Date: Mon, 12 Jan 2009 16:15:51 -0800 [thread overview]
Message-ID: <496BDD37.7030005@sgi.com> (raw)
In-Reply-To: <20090112222123.GB15294@elte.hu>
Ingo Molnar wrote:
> * Mike Travis <travis@sgi.com> wrote:
>
>> Ingo - should I push these to tip/cpus4096 via the cpus4096-for-ingo
>> tree since that has the relevant changes to irq_desc? Or by some other
>> means?
>
> yes, please update cpus4096-for-ingo so that i can pull it from your tree.
>
> Ingo
Hi Ingo,
Here's the consolidated patches for the irq_desc cpumask changes. There was
one small test merge conflict w/tip-master in kernel/irq/handle.c that I was not
sure how to 'pre-fix' from this end.
Also, I'm still hunting down that mail about the cross build tools.
Thanks!
Mike
The following changes since commit 28e08861b9afab4168b758fb7b95aa7a4da0f668:
Christophe Saout (1):
xen: fix too early kmalloc call
are available in the git repository at:
ssh://master.kernel.org/pub/scm/linux/kernel/git/travis/linux-2.6-cpus4096-for-ingo.git master
Mike Travis (1):
irq: update all arches for new irq_desc
arch/alpha/kernel/irq.c | 2 +-
arch/arm/kernel/irq.c | 18 ++++++++++++------
arch/arm/oprofile/op_model_mpcore.c | 2 +-
arch/blackfin/kernel/irqchip.c | 5 +++++
arch/ia64/kernel/iosapic.c | 2 +-
arch/ia64/kernel/irq.c | 4 ++--
arch/ia64/kernel/msi_ia64.c | 4 ++--
arch/ia64/sn/kernel/msi_sn.c | 2 +-
arch/mips/include/asm/irq.h | 2 +-
arch/mips/kernel/irq-gic.c | 2 +-
arch/mips/kernel/smtc.c | 2 +-
arch/mips/mti-malta/malta-smtc.c | 5 +++--
arch/parisc/kernel/irq.c | 8 ++++----
arch/powerpc/kernel/irq.c | 2 +-
arch/powerpc/platforms/pseries/xics.c | 5 +++--
arch/powerpc/sysdev/mpic.c | 3 ++-
arch/sparc/kernel/irq_64.c | 5 +++--
17 files changed, 44 insertions(+), 29 deletions(-)
next prev parent reply other threads:[~2009-01-13 0:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 22:05 [PATCH 0/8] irq: update all archs to use new irq_desc cpumask_var_t's Mike Travis
2009-01-12 22:05 ` [PATCH 1/8] alpha irq: update alpha for new irq_desc Mike Travis
2009-01-12 22:05 ` [PATCH 2/8] arm irq: update arm " Mike Travis
2009-01-12 22:05 ` [PATCH 3/8] blackfin irq: update blackfin " Mike Travis
2009-01-12 22:05 ` [PATCH 4/8] ia64 irq: update ia64 " Mike Travis
2009-01-12 22:05 ` [PATCH 5/8] mips irq: update mips " Mike Travis
2009-01-12 22:05 ` [PATCH 6/8] parisc irq: update parisc " Mike Travis
2009-01-13 6:04 ` Kyle McMartin
2009-01-12 22:05 ` [PATCH 7/8] powerpc irq: update powerpc " Mike Travis
2009-01-12 22:05 ` [PATCH 8/8] sparc irq: update sparc " Mike Travis
2009-01-12 22:07 ` [PATCH 0/8] irq: update all archs to use new irq_desc cpumask_var_t's Mike Frysinger
2009-01-13 1:21 ` Mike Travis
2009-01-13 1:25 ` Mike Frysinger
2009-01-12 22:20 ` Ingo Molnar
2009-01-12 22:21 ` Ingo Molnar
2009-01-12 22:31 ` Mike Travis
2009-01-12 22:52 ` Ingo Molnar
2009-01-13 0:15 ` Mike Travis [this message]
2009-01-14 11:14 ` Ingo Molnar
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=496BDD37.7030005@sgi.com \
--to=travis@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=steiner@sgi.com \
/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