From: Linus Torvalds <torvalds@linux-foundation.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] PCI changes for 2.6.34 - pci rom rom fail list
Date: Mon, 1 Mar 2010 08:05:55 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1003010803360.3616@localhost.localdomain> (raw)
In-Reply-To: <4B8B0113.1020103@kernel.org>
On Sun, 28 Feb 2010, Yinghai Lu wrote:
>
> [PATCH] pci: don't reassign to ROM res if it is not going to be enabled
>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Yes, this makes my setup work again.
I'm still nervous that it will cause problem on some _other_ machines
(because of not knowing that some bridge is transparent and then trying to
re-allocate things unnecessarily and causing chaos), but at least it seems
to be ok on this machine.
So I do have this nagging feeling that we'll still end up having to do
this whole "reassign PCI buses" thing as a kernel command line option and
default to not doing it, but let's give it a chance.
Linus
next prev parent reply other threads:[~2010-03-01 16:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 17:39 [git pull] PCI changes for 2.6.34 Jesse Barnes
2010-02-28 20:34 ` Linus Torvalds
2010-02-28 20:46 ` Linus Torvalds
2010-02-28 21:11 ` Yinghai
2010-02-28 21:19 ` Linus Torvalds
2010-02-28 22:41 ` Yinghai Lu
2010-02-28 23:49 ` [git pull] PCI changes for 2.6.34 - pci rom rom fail list Yinghai Lu
2010-03-01 6:28 ` Jesse Barnes
2010-03-01 16:05 ` Linus Torvalds [this message]
2010-03-01 16:35 ` Jesse Barnes
2010-03-01 17:38 ` Jesse Barnes
2010-02-28 23:51 ` [git pull] PCI changes for 2.6.34 -- pci_try_num Yinghai Lu
2010-03-01 1:16 ` [git pull] PCI changes for 2.6.34 Arjan van de Ven
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.00.1003010803360.3616@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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
Powered by JetHome