All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: jacob pan <jacob.jun.pan@linux.intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Feng Tang <feng.tang@intel.com>, Alan Cox <alan@linux.intel.com>,
	Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [PATCH v2] x86/mrst: correct pin to irq mapping
Date: Tue, 12 Apr 2011 08:35:38 +0200	[thread overview]
Message-ID: <20110412063538.GD31050@elte.hu> (raw)
In-Reply-To: <20110411094330.69c86910@jacob-laptop>


* jacob pan <jacob.jun.pan@linux.intel.com> wrote:

> Without the patch, kernel will crash during boot on Moorestown since the 
> secondary CPU clockevent (apbt1) will fail to request irq#1, which does not 
> have ioapic chip in its irq_desc[] entry. So, I would think this is an urgent 
> bug fix for 39.

Ok, just for future reference, this information is like 10x more important than 
*any* of the other information you presented in various changelog versions of 
this patch! I do not have this hardware so i had no idea how severe the problem 
was in practice - whether it's cosmetic, performance related or stability 
related.

I'll push your urgent fix to Linus via tip:x86/urgent.

Thanks,

	Ingo

  reply	other threads:[~2011-04-12  6:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 18:23 [PATCH v2] x86/mrst: correct pin to irq mapping Jacob Pan
2011-04-10  6:01 ` Ingo Molnar
2011-04-11 16:43   ` jacob pan
2011-04-12  6:35     ` Ingo Molnar [this message]
2011-04-12  7:40 ` [tip:x86/urgent] x86/mrst: Fix boot crash caused by incorrect " tip-bot for Jacob Pan

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=20110412063538.GD31050@elte.hu \
    --to=mingo@elte.hu \
    --cc=alan@linux.intel.com \
    --cc=arjan@linux.intel.com \
    --cc=feng.tang@intel.com \
    --cc=hpa@zytor.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.