From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: bzolnier@gmail.com
Cc: linux-ide@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] siimage: PIO1/2 taskfile transfer overclocking fix
Date: Sun, 28 Jan 2007 23:48:35 +0300 [thread overview]
Message-ID: <45BD0C23.8000004@ru.mvista.com> (raw)
In-Reply-To: <200701282346.55935.sshtylyov@ru.mvista.com>
Hello, I wrote:
> Fix two typos found by SiI680A documentation check. They caused the taskfile
> transfer overclocking:
>
> - in PIO mode 1 as 0x2283 must be used for both data and taskfile transfers;
>
> - in PIO mode 2 as data and taskfile timings are swapped when writing to the
> MMIO regs.
>
> Fix coding style and trailing whitespace in enclosing statements while at it...
>
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Forgot to specify that this patch was against Linus' tree...
MBR, Sergei
next prev parent reply other threads:[~2007-01-28 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-28 20:46 [PATCH] siimage: PIO1/2 taskfile transfer overclocking fix Sergei Shtylyov
2007-01-28 20:48 ` Sergei Shtylyov [this message]
[not found] ` <58cb370e0702021327x8d7bb77uaf949ee91b26b14d@mail.gmail.com>
2007-02-02 21:46 ` Fwd: " Bartlomiej Zolnierkiewicz
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=45BD0C23.8000004@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--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 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.