mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Takao Indoh <indou.takao@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	Milton Miller <miltonm@bga.com>, Jens Axboe <axboe@kernel.dk>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	WANG Cong <xiyou.wangcong@gmail.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] generic-ipi: Initialize call_single_queue before enabling interrupt
Date: Fri, 17 Jun 2011 10:19:11 +0200	[thread overview]
Message-ID: <20110617081911.GB893@elte.hu> (raw)
In-Reply-To: <ABCC2C38C9CAC4indou.takao@jp.fujitsu.com>


* Takao Indoh <indou.takao@jp.fujitsu.com> wrote:

> Just a reminder...
> 
> Thanks for acks, but I'm still waiting for inclusion.
> I tested 3.0.0-rc3 and kdump still failed due to pending IPI
> from 1st kernel. Need this patch to fix it.

For any future patch that has a review discussion (like this one) 
please collect Acks and resend the patch with the acks included once 
the discussion results in a final patch, otherwise maintainers might 
skip the patch as "still being reviewed".

I've collected the acks here and started testing your patch.

Thanks,

	Ingo

  reply	other threads:[~2011-06-17  8:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 16:35 Takao Indoh
2011-03-30 15:19 ` Américo Wang
2011-03-30 15:48 ` Neil Horman
2011-04-06 20:47 ` Vivek Goyal
2011-04-06 22:47   ` Takao Indoh
2011-04-06 22:52     ` Takao Indoh
2011-04-07 13:40       ` Vivek Goyal
2011-06-16 15:19 ` Takao Indoh
2011-06-17  8:19   ` Ingo Molnar [this message]
2011-06-17 15:11     ` Takao Indoh
2011-06-18 21:05 ` [tip:sched/urgent] generic-ipi: Fix kexec boot crash by initializing call_single_queue before enabling interrupts tip-bot for Takao Indoh

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=20110617081911.GB893@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=indou.takao@jp.fujitsu.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miltonm@bga.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=vgoyal@redhat.com \
    --cc=xiyou.wangcong@gmail.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®