From: Krzysztof Halasa <khc@pm.waw.pl>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Tejun Heo <htejun@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: NV SATA breakage: jgarzik/libata-dev#upstream etc
Date: Tue, 26 Sep 2006 01:50:32 +0200 [thread overview]
Message-ID: <m3fyef1p6f.fsf@defiant.localdomain> (raw)
In-Reply-To: <45185625.4050906@pobox.com> (Jeff Garzik's message of "Mon, 25 Sep 2006 18:20:21 -0400")
Jeff Garzik <jgarzik@pobox.com> 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
next prev parent reply other threads:[~2006-09-25 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 18:57 NV SATA breakage: jgarzik/libata-dev#upstream etc Krzysztof Halasa
2006-09-25 0:25 ` Jeff Garzik
2006-09-25 12:51 ` Krzysztof Halasa
2006-09-25 17:15 ` Krzysztof Halasa
2006-09-25 22:20 ` Jeff Garzik
2006-09-25 23:50 ` Krzysztof Halasa [this message]
2006-09-25 23:52 ` Jeff Garzik
2006-09-26 0:29 ` Krzysztof Halasa
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=m3fyef1p6f.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--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