From: Daniel Drake <dsd@gentoo.org>
To: Andrew Morton <akpm@linux-foundation.org>, Greg KH <greg@kroah.com>
Cc: linux kernel list <linux-kernel@vger.kernel.org>,
matthew@wil.cx, andreas.eckstein@gmx.net,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: pci-disable-decoding-during-sizing-of-bars.patch no longer needed
Date: Sat, 16 Feb 2008 21:50:51 +0000 [thread overview]
Message-ID: <47B75ABB.8000005@gentoo.org> (raw)
Hi,
The patch titled pci-disable-decoding-during-sizing-of-bars.patch in -mm
was previously used as a candidate to fix a boot hang with Intel's Q35
chipset: https://bugs.gentoo.org/show_bug.cgi?id=198810
However, that particular issue is solved by commit a0ca9909609 in Linus
tree:
PCI x86: always use conf1 to access config space below 256 bytes
So unless there are other reasons for keeping
pci-disable-decoding-during-sizing-of-bars around, I think we can drop it.
Thanks,
Daniel
next reply other threads:[~2008-02-16 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 21:50 Daniel Drake [this message]
2008-02-16 22:00 ` pci-disable-decoding-during-sizing-of-bars.patch no longer needed Matthew Wilcox
2008-02-16 22:05 ` Andrew Morton
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=47B75ABB.8000005@gentoo.org \
--to=dsd@gentoo.org \
--cc=akpm@linux-foundation.org \
--cc=andreas.eckstein@gmx.net \
--cc=greg@kroah.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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