All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Bart Hartgers <bart.hartgers@gmail.com>
Cc: Tejun Heo <htejun@gmail.com>,
	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
Subject: Re: [patch 2/2] sata_via: Delay on vt6420 when starting ATAPI DMA write
Date: Sat, 13 Feb 2010 17:47:53 -0500	[thread overview]
Message-ID: <4B772C19.90501@pobox.com> (raw)
In-Reply-To: <4B56A8C9.2000807@gmail.com>

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?


  reply	other threads:[~2010-02-13 22:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16 23:56 [patch 0/2] sata_via: bugfixes for vt6420 and vt6421 Bart Hartgers
2010-01-16 23:56 ` [patch 1/2] sata_via: Correctly setup PIO/DMA for pata slave on vt6421 Bart Hartgers
2010-01-20  3:33   ` Tejun Heo
2010-01-20 19:35   ` Jeff Garzik
2010-01-16 23:56 ` [patch 2/2] sata_via: Delay on vt6420 when starting ATAPI DMA write Bart Hartgers
2010-01-20  3:30   ` Tejun Heo
2010-01-20  4:53     ` Robert Hancock
2010-01-20  6:33       ` Bart Hartgers
2010-01-20  6:33         ` Bart Hartgers
2010-01-20  6:54         ` Tejun Heo
2010-01-20 10:43           ` Bart Hartgers
2010-01-20 10:43             ` Bart Hartgers
2010-01-20  6:44     ` Bart Hartgers
2010-01-20  6:44       ` Bart Hartgers
2010-01-20  6:55       ` Tejun Heo
2010-02-13 22:47         ` Jeff Garzik [this message]
2010-02-14 11:20           ` Bart Hartgers

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=4B772C19.90501@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=apopov@sirma.bg \
    --cc=bart.hartgers@gmail.com \
    --cc=david@coomber.co.za \
    --cc=htejun@gmail.com \
    --cc=jay4mail@gmail.com \
    --cc=juergen.metzdorf@telelev-dsl.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markpschool@hotmail.com \
    --cc=sporadic.crash@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.