From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-ide@vger.kernel.org, Johannes Resch <jr@xor.at>
Subject: Re: Inclusion of patch for Promise SATAII 150 TX4 in mainline 2.6 kernel?
Date: Mon, 07 Feb 2005 16:39:00 -0500 [thread overview]
Message-ID: <4207DFF4.8010208@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0502071601140.31011-100000@coffee.psychology.mcmaster.ca>
Mark Hahn wrote:
>>has no builtin support for Promise SATAII 150 TX4 yet; a separate patch
>>(http://marc.theaimsgroup.com/?l=linux-ide&m=110426005503319&q=raw) is
>>needed to recognize this hardware.
>
>
> I had good luck with this patch as well. I think the SATA-SMART patches
> should go in too, even if they aren't perfect yet...
The Promise SATAII patch went in today.
The SMART patches absolutely -should not- go in. Certain common hdparm
commands can cause data corruption rather than produce expected results.
Jeff
next prev parent reply other threads:[~2005-02-07 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 13:39 Inclusion of patch for Promise SATAII 150 TX4 in mainline 2.6 kernel? Johannes Resch
2005-02-07 21:03 ` Mark Hahn
2005-02-07 21:39 ` Jeff Garzik [this message]
2005-02-08 4:19 ` Brad Campbell
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=4207DFF4.8010208@pobox.com \
--to=jgarzik@pobox.com \
--cc=hahn@physics.mcmaster.ca \
--cc=jr@xor.at \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).