From: Jeff Garzik <jeff@garzik.org>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: sata_via: write errors on PATA drive connected to VT6421
Date: Sat, 01 Sep 2007 06:52:36 -0400 [thread overview]
Message-ID: <46D94474.7080905@garzik.org> (raw)
In-Reply-To: <200709010055.22200.linux@rainbow-software.org>
Ondrej Zary wrote:
> Hello,
> I think that I've found and fixed the problem. There is a copy/paste bug in
> vt6421_set_dma_mode() function which causes wrong values to be written to
> PATA_UDMA_TIMING register.
>
>
> This patch fixes a copy/paste bug that breaks DMA modes on VT6421 PATA port.
>
> Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
applied
prev parent reply other threads:[~2007-09-01 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 20:42 sata_via: write errors on PATA drive connected to VT6421 Ondrej Zary
2007-08-21 12:27 ` Alan Cox
2007-08-21 17:09 ` Ondrej Zary
2007-08-31 22:55 ` Ondrej Zary
2007-08-31 23:19 ` Alan Cox
2007-09-01 10:52 ` Jeff Garzik [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=46D94474.7080905@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.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).