public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yinghai Lu <yinghai@kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>, Tejun Heo <tj@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [git pull] first round of PCI updates for 2.6.32
Date: Fri, 18 Sep 2009 09:17:05 -0700	[thread overview]
Message-ID: <20090918091705.65478530@jbarnes-g45> (raw)
In-Reply-To: <20090918155247.GA20347@elte.hu>

On Fri, 18 Sep 2009 17:52:47 +0200
Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> 
> > On Thu, 17 Sep 2009 19:59:44 +0200
> > Ingo Molnar <mingo@elte.hu> wrote:
> > 
> > > 
> > > * Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > > 
> > > > On Thu, 17 Sep 2009 19:30:12 +0200
> > > > Ingo Molnar <mingo@elte.hu> wrote:
> > > > 
> > > > > 
> > > > > * Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > 
> > > > > Config and full bootlog attached.
> > > > > 
> > > > > Note:
> > > > > 
> > > > >  CONFIG_DEBUG_PER_CPU_MAPS=y
> > > > >  CONFIG_CPUMASK_OFFSTACK=y
> > > > 
> > > > Does this patch fix it?  I sent it to you earlier but I never
> > > > heard back...
> > > 
> > > Ah ... you probably sent it in the merge window communication
> > > blackout ;-)
> > > 
> > > Will try, thanks.
> > 
> > Did you get a chance to try this patch yet Ingo?
> 
> Yeah, it does - thanks.
> 

Thanks for testing, just pushed out the fix to my tree.

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2009-09-18 16:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 20:21 [git pull] first round of PCI updates for 2.6.32 Jesse Barnes
2009-09-16 14:55 ` Linus Torvalds
2009-09-16 15:20   ` Stephen Rothwell
2009-09-17 17:30 ` Ingo Molnar
2009-09-17 17:36   ` Jesse Barnes
2009-09-17 17:59     ` Ingo Molnar
2009-09-17 18:46       ` Jesse Barnes
2009-09-18  7:59         ` [crash] BUG: unable to handle kernel NULL pointer dereference at (null), last sysfs file: /sys/devices/pci0000:00/0000:00:01.0/local_cpus Ingo Molnar
2009-09-18  9:37           ` David Rientjes
2009-09-18 15:38           ` Linus Torvalds
2009-09-18 15:44             ` Jesse Barnes
2009-09-24  8:18             ` Rusty Russell
2009-09-24 12:18               ` [tip:x86/urgent] x86: Remove redundant non-NUMA topology functions tip-bot for Rusty Russell
2009-09-18 16:24           ` [crash] BUG: unable to handle kernel NULL pointer dereference at (null), last sysfs file: /sys/devices/pci0000:00/0000:00:01.0/local_cpus Yinghai Lu
2009-09-18 16:34             ` Jesse Barnes
2009-09-18 16:51             ` Linus Torvalds
2009-09-18 17:10               ` Jesse Barnes
2009-09-18 15:27       ` [git pull] first round of PCI updates for 2.6.32 Jesse Barnes
2009-09-18 15:52         ` Ingo Molnar
2009-09-18 16:17           ` Jesse Barnes [this message]
2009-09-17 17:45   ` Yinghai Lu
2009-09-17 18:31     ` 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=20090918091705.65478530@jbarnes-g45 \
    --to=jbarnes@virtuousgeek.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@kernel.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