From: Jeff Garzik <jeff@garzik.org>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: cirrus ep93xx pata driver
Date: Mon, 28 May 2007 21:27:10 -0400 [thread overview]
Message-ID: <465B816E.5060407@garzik.org> (raw)
In-Reply-To: <20070128202117.GA6147@xi.wantstofly.org>
I know it's probably a low priority, but could you rediff this against
the current libata?
I'm wondering where we are in terms of hooks that you need. Since you
posted this we added some hooks for the pata_scc driver, most notably
->irq_on() hooks. And other code you modify, such as the
ata_bus_reset() function, is slated for deletion once all drivers have
been converted over to the new EH (done, in testing).
I'm betting libata-core only has a little way to go before pata_ep93xx
will work.
Jeff
next prev parent reply other threads:[~2007-05-29 1:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 11:01 PATA drivers queued for 2.6.19 Jeff Garzik
2006-09-04 12:02 ` Grant Coady
2006-09-04 12:07 ` Jan Engelhardt
2006-09-04 12:35 ` Tomasz Torcz
2006-09-04 13:35 ` Jan Engelhardt
2006-09-05 13:26 ` Helge Hafting
2006-09-05 14:39 ` Alan Cox
2006-09-05 16:51 ` Grant Coady
2006-09-05 17:57 ` Krzysztof Halasa
2006-09-05 21:24 ` Grant Coady
2006-09-04 12:12 ` Jeff Garzik
2006-09-04 13:27 ` Alan Cox
2006-09-04 12:02 ` Alan Cox
2006-09-04 12:10 ` Jan Engelhardt
2006-09-04 12:15 ` Jeff Garzik
2006-09-05 13:30 ` John Stoffel
2006-09-05 13:46 ` Sergei Shtylyov
2006-09-05 15:10 ` John Stoffel
2006-09-05 20:48 ` Bill Davidsen
2006-09-06 7:48 ` Alan Cox
2006-09-04 21:31 ` Andras Mantia
2006-09-05 2:25 ` Jeff Garzik
2006-09-21 11:55 ` Lennert Buytenhek
2006-09-22 9:51 ` Jeff Garzik
2007-01-28 20:21 ` cirrus ep93xx pata driver (was: Re: PATA drivers queued for 2.6.19) Lennert Buytenhek
2007-05-29 1:27 ` Jeff Garzik [this message]
2007-05-29 1:48 ` cirrus ep93xx pata driver Lennert Buytenhek
2007-05-29 2:58 ` Jeff Garzik
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=465B816E.5060407@garzik.org \
--to=jeff@garzik.org \
--cc=buytenh@wantstofly.org \
--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).