[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49697306.9040103@sgi.com>
Date: Sat, 10 Jan 2009 20:18:14 -0800
From: Mike Travis <travis@....com>
To: Ingo Molnar <mingo@...e.hu>
CC: Matt Mackall <mpm@...enic.com>, Yinghai Lu <yinghai@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] sparseirq: make some func to be used with genirq
Ingo Molnar wrote:
> * Mike Travis <travis@....com> wrote:
>
>> Ingo Molnar wrote:
>>> * Matt Mackall <mpm@...enic.com> wrote:
>>>
>>>> On Thu, 2009-01-08 at 13:06 +0100, Ingo Molnar wrote:
>>>>> (Matt Cc:-ed)
>>>>>
>>>>> Matt, does this look good to you? The point of this cleanup would be to
>>>>> make desc->timer_rand_state depend on hardirq (the presence of irq_desc[])
>>>>> - not sparseirq (which does not make much sense).
>>>> Seems fine.
>>>>
>>>> Signed-off-by: Matt Mackall <mpm@...enic.com>
>>> applied it to tip/irq/urgent, thanks guys!
>>>
>>> Ingo
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>> the body of a message to majordomo@...r.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>> Please read the FAQ at http://www.tux.org/lkml/
>> This will conflict with the change of kstat_irqs from unsigned int to
>> unsigned long.
>>
>> If you do your magic on tip/cpus4096, I will git-remote update my tree
>> and make the conflict go away...
>
> you can defer the change to unsigned long to a later stage, when these
> have hit upstream. (in a few days)
>
> Ingo
Good idea since the change to long tripped a panic in the CPUMASK_OFFSTACK=n
case (which doesn't make a lot of sense at this moment.)
Will push the remainder soon.
Thanks,
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists