mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "KOSAKI Motohiro" <kosaki.motohiro@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Jesse Barnes" <jbarnes@virtuousgeek.org>
Subject: Re: [git pull] sparseirq / irq updates for v2.6.29
Date: Sun, 28 Dec 2008 02:27:43 +0900	[thread overview]
Message-ID: <2f11576a0812270927taef068fobbad997dc5e5aacf@mail.gmail.com> (raw)
In-Reply-To: <20081227133240.GA8716@elte.hu>

> ------------------>
> Ingo Molnar (2):
>      sparseirq: do not printk when migrating IRQ descriptors
>      sparseirq: fix desc->lock init
>
> KOSAKI Motohiro (4):
>      hrtimer: remove #include <linux/irq.h>
>      irq: for_each_irq_desc() move to irqnr.h
>      proc: remove ifdef CONFIG_SPARSE_IRQ from stat.c
>      irq: simplify for_each_irq_desc() usage
>
> Yinghai Lu (4):
>      sparseirq: remove duplicated arch_early_irq_init()
>      sparseirq: work around compiler optimizing away __weak functions

Unfortunately, this workaround doesn't workaround.
Kamalesh reported kernel still crashes.

So, I suggest to pending this pull request awhile.
Nobody want to merge pseudo fix.



>      sparseirq: fix hang with !SPARSE_IRQ
>      sparseirq: set lock_class for legacy irq when sparse_irq is selected

  reply	other threads:[~2008-12-27 17:27 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-25 16:07 Ingo Molnar
2008-12-27 13:32 ` Ingo Molnar
2008-12-27 17:27   ` KOSAKI Motohiro [this message]
2008-12-27 17:38     ` Ingo Molnar
2008-12-28 23:11       ` Linus Torvalds
2008-12-28 23:23         ` Yinghai Lu
2008-12-28 23:27         ` Ingo Molnar
2008-12-28 23:30           ` Ingo Molnar
2008-12-29  0:01             ` Yinghai Lu
2008-12-29  8:39               ` KOSAKI Motohiro
2008-12-29 11:09                 ` Ingo Molnar
2008-12-29 11:20                   ` KOSAKI Motohiro
2008-12-29  0:28             ` Yinghai Lu
2008-12-29  0:53               ` Yinghai Lu
2008-12-29  9:44                 ` Ingo Molnar
2008-12-29  9:52                   ` Ingo Molnar
2008-12-29 11:00             ` Kamalesh Babulal
2008-12-29 11:05               ` Ingo Molnar
2008-12-29 16:05                 ` Kamalesh Babulal
2008-12-29 16:20                   ` Ingo Molnar
2008-12-29 16:22                   ` KOSAKI Motohiro
2008-12-29 16:36                     ` Ingo Molnar
2008-12-28 23:55           ` H. Peter Anvin
2008-12-29  0:06             ` Yinghai Lu
2008-12-29  0:38               ` H. Peter Anvin
2008-12-29  9:34               ` Ingo Molnar
2008-12-28 23:10   ` [git pull] sparseirq / irq fixes Ingo Molnar
2008-12-29 12:52     ` Ingo Molnar
2008-12-31  0:22       ` Linus Torvalds
2008-12-31  6:48         ` Ingo Molnar
2008-12-31 12:00 ` [sparseirq] remove debug printks (io_apic.c) Markus Trippelsdorf
2009-01-02 22:21   ` 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=2f11576a0812270927taef068fobbad997dc5e5aacf@mail.gmail.com \
    --to=kosaki.motohiro@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®