From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] pata_hpt3xx: Updates to match work done by Sergei to old IDE
Date: Tue, 17 Apr 2007 10:47:09 -0400 [thread overview]
Message-ID: <4624DDED.9080200@garzik.org> (raw)
In-Reply-To: <20070411001649.1abecf4b@the-village.bc.nu>
Alan Cox wrote:
> Signed-off-by: Alan Cox <alan@redhat.com>
>
> Correct timing lists
> Use DPLL when appropriate
> Fix HPT372 UDMA 100 limit
> Add HPT371N support
> Reset the correct channel only not both when doing the pre_reset
> processing
> Pull DPLL clock from I/O not PCI space
> Correct DPLL failure error handling
Looks OK to me, but... should I still apply this, given the recent
regression reports that hit LKML less than 48 hours ago?
next prev parent reply other threads:[~2007-04-17 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 23:16 [PATCH] pata_hpt3xx: Updates to match work done by Sergei to old IDE Alan Cox
2007-04-17 14:47 ` Jeff Garzik [this message]
2007-04-17 14:51 ` Alan Cox
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=4624DDED.9080200@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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).