From: Matthew Wilcox <matthew@wil.cx>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Matthew Wilcox <matthew@wil.cx>, Greg KH <greg@kroah.com>,
Linus Torvalds <torvalds@osdl.org>,
Andrew Morton <akpm@zip.com.au>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
parisc-linux@parisc-linux.org
Subject: Re: [PATCH] Sort generic PCI fixups after specific ones
Date: Tue, 5 Oct 2004 16:29:59 +0100 [thread overview]
Message-ID: <20041005152959.GX16153@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20041002014817.A24292@jurassic.park.msu.ru>
On Sat, Oct 02, 2004 at 01:48:17AM +0400, Ivan Kokshaysky wrote:
> On Thu, Sep 30, 2004 at 06:41:55PM +0100, Matthew Wilcox wrote:
> > Allow prioritising PCI fixups. "How it works" is covered in the comment
> > in pci.h. The patch to superio.c may well only apply with fuzz to the
> > current Linux tree; I include it only to show an example.
>
> No, you missed my point.
> What we need is yet another PCI fixup *pass*, not prioritizing fixups
> inside *one* pass - see appended patch (compile tested only).
Boot tested. Works fine for my problem child. Greg, can you apply
Ivan's patch, please?
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
prev parent reply other threads:[~2004-10-05 15:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 21:43 Matthew Wilcox
2004-09-23 16:03 ` [parisc-linux] " Joel Soete
2004-09-23 17:20 ` Greg KH
2004-09-23 17:31 ` Matthew Wilcox
2004-09-23 22:33 ` Ivan Kokshaysky
2004-09-30 17:41 ` Matthew Wilcox
2004-10-01 15:13 ` [parisc-linux] " Joel Soete
2004-10-01 21:48 ` Ivan Kokshaysky
2004-10-05 15:29 ` Matthew Wilcox [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=20041005152959.GX16153@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=akpm@zip.com.au \
--cc=greg@kroah.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=parisc-linux@parisc-linux.org \
--cc=torvalds@osdl.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