From: Linus Torvalds <torvalds@linux-foundation.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Ingo Molnar <mingo@elte.hu>, dann frazier <dannf@hp.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, Stephen Frost <sfrost@snowman.net>
Subject: Re: [PATCH] x86/pci: insert ioapic resource before assign unassigned resource for pci -v2
Date: Fri, 10 Jul 2009 14:27:09 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0907101426490.3352@localhost.localdomain> (raw)
In-Reply-To: <4A576E04.9070004@kernel.org>
On Fri, 10 Jul 2009, Yinghai Lu wrote:
>
> solution is trying to insert ioapic_resource early a little bit.
>
> v2: update comments
Ack, looks sane to me.
Linus
prev parent reply other threads:[~2009-07-10 21:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 18:03 mptsas, msi and the dl585 g2 dann frazier
2009-06-30 18:35 ` Yinghai Lu
2009-07-03 22:57 ` dann frazier
2009-07-04 19:30 ` Yinghai Lu
2009-07-06 16:57 ` dann frazier
2009-07-09 18:59 ` dann frazier
2009-07-09 19:17 ` Yinghai Lu
2009-07-09 19:34 ` Yinghai Lu
2009-07-09 19:48 ` Yinghai Lu
2009-07-09 20:40 ` James Bottomley
2009-07-09 21:12 ` Yinghai Lu
2009-07-09 21:41 ` [PATCH} x86/pci: insert ioapic resource before assign unassigned resource for pci Yinghai Lu
2009-07-09 22:01 ` dann frazier
2009-07-10 16:36 ` [PATCH] x86/pci: insert ioapic resource before assign unassigned resource for pci -v2 Yinghai Lu
2009-07-10 20:03 ` Jesse Barnes
2009-07-10 21:27 ` Linus Torvalds [this message]
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=alpine.LFD.2.01.0907101426490.3352@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=dannf@hp.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfrost@snowman.net \
--cc=tglx@linutronix.de \
--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