From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bart Hartgers Subject: Re: [patch 2/2] sata_via: Delay on vt6420 when starting ATAPI DMA write Date: Sun, 14 Feb 2010 12:20:14 +0100 Message-ID: <4B77DC6E.8070902@gmail.com> References: <20100116235653.898098245@gmail.com> <20100116235851.884756038@gmail.com> <4B5678E2.2050709@gmail.com> <7eb6a4d81001192244k19d28805p9cb4eaec7eed9366@mail.gmail.com> <4B56A8C9.2000807@gmail.com> <4B772C19.90501@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail-vw0-f46.google.com ([209.85.212.46]:65078 "EHLO mail-vw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754051Ab0BNLUf (ORCPT ); Sun, 14 Feb 2010 06:20:35 -0500 In-Reply-To: <4B772C19.90501@pobox.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Jeff Garzik Cc: Tejun Heo , linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org, juergen.metzdorf@telelev-dsl.de, markpschool@hotmail.com, sporadic.crash@gmail.com, apopov@sirma.bg, david@coomber.co.za, jay4mail@gmail.com Jeff Garzik wrote: > On 01/20/2010 01:55 AM, Tejun Heo wrote: >> Hello, >> >> On 01/20/2010 03:44 PM, Bart Hartgers wrote: >>> Yes, you're right. I'll drop the printk_once and send another patch >>> for inclusion. However, for testing I found it very useful to make >>> sure that I got the right module loaded. So I figured it could be >>> helpful for the interpretation of success/failure reports. >> >> Oh yeah, for testing, having it there is a good idea. >> >>> Assuming that this patch works for other people as well, what is >>> prefered: resending both patches or just to make a new #2/2 (the >>> vt6420 one)? >> >> I think just re-doing the second patch should be enough. > > Agreed... ping, Bart? > Hi Jeff, I was waiting for some feedback on whether this patch actually solves the problem for others as well. Unfortunately, I didn't get any response so far, that's why I didn't resend the patch yet. But I guess it doesn't make sense to wait any longer, so I'll redo the patch and send it in a separate mail in a few minutes. (I also tried searching for people suffering from this bug in the past 3 months, and couldn't find any. I _did_ see some recent posts on various bug-lists by Tejun asking to test my patch, but again no response.) Groeten, Bart