mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jack Steiner <steiner@sgi.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/8] irq: update all archs to use new irq_desc cpumask_var_t's.
Date: Mon, 12 Jan 2009 14:05:19 -0800	[thread overview]
Message-ID: <20090112220519.566749000@polaris-admin.engr.sgi.com> (raw)


Impact: cleanup, use new cpumask API.

Minor cleanup to use the new affinity and pending_mask cpumask_var_t's
in irq_desc:

	alpha irq: update alpha for new irq_desc
	arm irq: update arm for new irq_desc
	blackfin irq: update blackfin for new irq_desc
	ia64 irq: update ia64 for new irq_desc
	mips irq: update mips for new irq_desc
	parisc irq: update parisc for new irq_desc
	powerpc irq: update powerpc for new irq_desc
	arm irq: update arm for new irq_desc

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?

Based on tip/cpus4096: v2.6.29-rc1-19-g92296c6

[I'm setting up the cross-compile toolchain and will verify (as much as I
can) that the above builds correctly.]

Signed-off-by: Mike Travis <travis@sgi.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Bryan Wu <cooloney@kernel.org>
Cc: David S. Miller <davem@davemloft.net>
Cc: Grant Grundler <grundler@parisc-linux.org>
Cc: Kyle McMartin <kyle@mcmartin.ca>
Cc: Matthew Wilcox <matthew@wil.cx>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Richard Henderson <rth@twiddle.net>
Cc: Tony Luck <tony.luck@intel.com>
Cc: <kernel@wantstofly.org>
Cc: <linuxppc-dev@ozlabs.org>
Cc: <linux-ia64@vger.kernel.org>
Cc: <linux-mips@linux-mips.org>
Cc: <linux-parisc@vger.kernel.org>
Cc: <sparclinux@vger.kernel.org>

-- 

             reply	other threads:[~2009-01-12 22:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 22:05 Mike Travis [this message]
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
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=20090112220519.566749000@polaris-admin.engr.sgi.com \
    --to=travis@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®