From: Tejun Heo <htejun@gmail.com>
To: kanniball@zmail.pt
Cc: linux-ide@vger.kernel.org
Subject: Re: Sil3112 bugfix: wich one???
Date: Tue, 17 May 2005 10:21:35 +0900 [thread overview]
Message-ID: <4289471F.1050402@gmail.com> (raw)
In-Reply-To: <200505170043.28320.kanniball@zmail.pt>
Kanniball wrote:
> Nobody can answer me???
> Jeff, Tejun...
>
> On Wednesday 04 May 2005 16:24, Kanniball wrote:
>
>>Hi!
>>
>>There are two patches for fixing the problem with Silicon Image 311x SATA
>>controllers, one from Silicon Image and other from Tejun Heo.
>>Wich one "we" should apply?
>>
>>Thanks for your patience and for your work!
>>
>>Best regards,
>>
>>Paulo Fidalgo, aka Kanniball
>>
Hi,
I think I've replied but I'm pretty delusional. :-)
The two patches are independent. Just apply both. AFAIK, the patch
from Silicon Image applies to only small number of equipments, and if
you were using the controller okay except for low performance, sil patch
wouldn't do much for you. But it can't hurt.
Thanks.
--
tejun
prev parent reply other threads:[~2005-05-17 1:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 16:24 Sil3112 bugfix: wich one??? Kanniball
2005-05-17 0:43 ` Kanniball
2005-05-17 1:21 ` Tejun Heo [this message]
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=4289471F.1050402@gmail.com \
--to=htejun@gmail.com \
--cc=kanniball@zmail.pt \
--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).