All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Mike Travis <travis@sgi.com>, Rusty Russell <rusty@rustcorp.com.au>
Cc: Dean Nelson <dcn@sgi.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Jack Steiner <steiner@sgi.com>,
	Alan Mayer <ajm@sgi.com>,
	jeremy@goop.org, rusty@rustcorp.com.au,
	suresh.b.siddha@intel.com, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Yinghai Lu <Yinghai.lu@amd.com>
Subject: Re: [PATCH 1/3] switch vector_irq[] from irq number to irq_desc pointer v2
Date: Mon, 22 Sep 2008 13:05:42 +0200	[thread overview]
Message-ID: <20080922110542.GD5987@elte.hu> (raw)
In-Reply-To: <48D40A97.2000402@sgi.com>


* Mike Travis <travis@sgi.com> wrote:

> Hi Ingo,
> 
> Note that my recent patch from a couple of weeks ago, stripped almost 
> all of the cpumask_t's from the io_apic functions.  Any chance we can 
> apply them before we add more?
> 
> I'd be willing to merge in Dean's patch over the top of mine (or 
> vice-versa).

i'm really looking forwards to Rusty's 'get-rid-of-cpumask_t use' 
patchset, which would solve such cpumask_t proliferation issues once and 
for all.

	Ingo

  parent reply	other threads:[~2008-09-22 11:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 20:02 [PATCH 0/3] unify the allocation of irq vectors v2 Dean Nelson
2008-09-19 20:04 ` [PATCH 1/3] switch vector_irq[] from irq number to irq_desc pointer v2 Dean Nelson
2008-09-19 20:24   ` Mike Travis
2008-09-19 23:17     ` Dean Nelson
2008-09-22 11:05     ` Ingo Molnar [this message]
2008-09-22 15:12       ` Mike Travis
2008-09-22 15:44         ` Mike Travis
2008-09-19 20:40   ` Yinghai Lu
2008-09-19 23:26     ` Dean Nelson
2008-09-19 20:06 ` [PATCH 2/3] switch static system vector allocation to use vector_irq[] v2 Dean Nelson
2008-09-19 20:08 ` [PATCH 3/3] switch non-standard SYSCALL_VECTOR allocation to use vector_irq v2 Dean Nelson

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=20080922110542.GD5987@elte.hu \
    --to=mingo@elte.hu \
    --cc=Yinghai.lu@amd.com \
    --cc=ajm@sgi.com \
    --cc=dcn@sgi.com \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=steiner@sgi.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=travis@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.