From: Oliver Neukum <oneukum@suse.de>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Michal Marek <mmarek@suse.cz>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Takashi Iwai <tiwai@suse.de>, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pciehp: Add pciehp_surprise module option
Date: Wed, 27 Mar 2013 17:11:39 +0100 [thread overview]
Message-ID: <5658592.BRAWLYK6e8@linux-5eaq.site> (raw)
In-Reply-To: <1363969243.24132.613.camel@bling.home>
On Friday 22 March 2013 10:20:43 Alex Williamson wrote:
> > (*) It would probably make more sense to have a list of dmi strings,
> > because it's the PCIe controller that does not set the capability bit
> > when it should. The device (Realtek card reader in this case) seems to
> > behave correctly. The machines in question have been laptops or
> > all-in-one PCs so far, so there should be no problem with dmi matches.
>
> Yep, I think that makes sense, leave the global option for debugging but
> fix individual known broken devices through dmi quirks. Thanks,
I checked with Win8 and it does ignore the surprise attribute.
Regards
Oliver
next prev parent reply other threads:[~2013-03-27 16:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 14:02 [PATCH] pciehp: Add pciehp_surprise module option Takashi Iwai
2013-03-20 16:33 ` Randy Dunlap
2013-03-20 16:39 ` Takashi Iwai
2013-03-20 17:52 ` Matthew Garrett
2013-03-20 19:11 ` Takashi Iwai
2013-03-20 19:12 ` Matthew Garrett
2013-03-20 19:23 ` Takashi Iwai
2013-03-20 19:26 ` Matthew Garrett
2013-03-20 18:09 ` Alex Williamson
2013-03-20 19:08 ` Takashi Iwai
2013-03-22 16:15 ` Michal Marek
2013-03-22 16:16 ` Matthew Garrett
2013-03-22 16:35 ` Michal Marek
2013-03-22 16:20 ` Alex Williamson
2013-03-27 16:11 ` Oliver Neukum [this message]
2013-03-27 16:19 ` Michal Marek
2013-03-20 18:41 ` Martin Mokrejs
2013-03-20 18:56 ` Martin Mokrejs
2013-03-20 19:20 ` Takashi Iwai
2013-06-07 0:04 ` Martin Mokrejs
2013-03-25 16:58 ` Bjorn Helgaas
2013-04-10 16:34 ` Takashi Iwai
2013-04-10 17:19 ` Bjorn Helgaas
2013-04-11 13:40 ` Takashi Iwai
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=5658592.BRAWLYK6e8@linux-5eaq.site \
--to=oneukum@suse.de \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=mmarek@suse.cz \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.