Andrew Morton wrote:
Stefan Richter <[email protected]> wrote:Of course we don't have a complete picture of which models are affected though.I suppose we could do both. As people are found who need the module parameter, we grab their DMI strings and add them to the table?
Jesse, what DMI_PRODUCT_NAME matches your laptop? -- Stefan Richter -=====-=-=-= =-=- =---= http://arcgraph.de/sr/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: ohci1394 unhandled interrupts bug in 2.6.14-rc2
- From: Jesse Barnes <[email protected]>
- Re: ohci1394 unhandled interrupts bug in 2.6.14-rc2
- References:
- ohci1394 unhandled interrupts bug in 2.6.14-rc2
- From: [email protected]
- Re: ohci1394 unhandled interrupts bug in 2.6.14-rc2
- From: Stefan Richter <[email protected]>
- Re: ohci1394 unhandled interrupts bug in 2.6.14-rc2
- From: Jesse Barnes <[email protected]>
- Re: ohci1394 unhandled interrupts bug in 2.6.14-rc2
- From: Andrew Morton <[email protected]>
- Re: ohci1394 unhandled interrupts bug in 2.6.14-rc2
- From: Stefan Richter <[email protected]>
- Re: ohci1394 unhandled interrupts bug in 2.6.14-rc2
- From: Andrew Morton <[email protected]>
- ohci1394 unhandled interrupts bug in 2.6.14-rc2
- Prev by Date: Re: [PATCH] ktimers subsystem 2.6.14-rc2-kt5
- Next by Date: Re: [patch 0/8] Nesting class_device patches that actually work
- Previous by thread: Re: ohci1394 unhandled interrupts bug in 2.6.14-rc2
- Next by thread: Re: ohci1394 unhandled interrupts bug in 2.6.14-rc2
- Index(es):
 |