From: Philip Langdale <philipl@mail.utexas.edu>
To: Greg KH <gregkh@suse.de>
Cc: bjdouma@xs4all.nl, linux-kernel@vger.kernel.org
Subject: Re: pci-pci-quirk-for-asus-a8v-and-a8v-deluxe-motherboards.patch
Date: Thu, 09 Mar 2006 23:20:36 -0800 [thread overview]
Message-ID: <441128C4.9020202@mail.utexas.edu> (raw)
In-Reply-To: <20060310063836.GA31213@suse.de>
Greg KH wrote:
>>
>> I'm not sure what the most efficient way to generalise it - especially
>> with cases like the Soyo one where there's no proper subvendor id.
>
> Great, thanks for the information. How about just adding new device ids
> for the new machines that also need this function called. It's quite
> easy to do that...
Actually, I would go as far as to say just drop the check for the
subsystem vendor completely and unconditionally read the pci config
byte.
--phil
prev parent reply other threads:[~2006-03-10 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 3:25 pci-pci-quirk-for-asus-a8v-and-a8v-deluxe-motherboards.patch Philip Langdale
2006-03-10 6:38 ` pci-pci-quirk-for-asus-a8v-and-a8v-deluxe-motherboards.patch Greg KH
2006-03-10 7:20 ` Philip Langdale [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=441128C4.9020202@mail.utexas.edu \
--to=philipl@mail.utexas.edu \
--cc=bjdouma@xs4all.nl \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.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