Jeff Garzik <[email protected]> writes: > Krzysztof Halasa wrote: >> ppi[0] = ppi[1] = &nv_port_info[ent->driver_data]; > > That's probably the best solution. It fixes the SATA NV problem (I'm not attaching the patch as you already posted similar one). -- Krzysztof Halasa - 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: NV SATA breakage: jgarzik/libata-dev#upstream etc
- From: Jeff Garzik <[email protected]>
- Re: NV SATA breakage: jgarzik/libata-dev#upstream etc
- References:
- NV SATA breakage: jgarzik/libata-dev#upstream etc
- From: Krzysztof Halasa <[email protected]>
- Re: NV SATA breakage: jgarzik/libata-dev#upstream etc
- From: Jeff Garzik <[email protected]>
- Re: NV SATA breakage: jgarzik/libata-dev#upstream etc
- From: Krzysztof Halasa <[email protected]>
- Re: NV SATA breakage: jgarzik/libata-dev#upstream etc
- From: Krzysztof Halasa <[email protected]>
- Re: NV SATA breakage: jgarzik/libata-dev#upstream etc
- From: Jeff Garzik <[email protected]>
- NV SATA breakage: jgarzik/libata-dev#upstream etc
- Prev by Date: Re: oops in :snd_pcm_oss:resample_expand+0x19c/0x1f0
- Next by Date: Re: NV SATA breakage: jgarzik/libata-dev#upstream etc
- Previous by thread: Re: NV SATA breakage: jgarzik/libata-dev#upstream etc
- Next by thread: Re: NV SATA breakage: jgarzik/libata-dev#upstream etc
- Index(es):