From: Tejun Heo <htejun@gmail.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH libata#upstream 2/2] sata_promise: separate SATA and PATA ops
Date: Mon, 12 Mar 2007 18:20:21 +0900 [thread overview]
Message-ID: <45F51B55.1050202@gmail.com> (raw)
In-Reply-To: <200703112020.l2BKKh5P018685@harpo.it.uu.se>
Mikael Pettersson wrote:
> This patch changes sata_promise so that the PATA ports
> on TX2plus chips are bound to the pdc_pata_ops structure.
> This means that operations called from the SATA ops
> structures don't need any SATA-vs-PATA tests any more.
> Instead, operations that depend on a port being SATA or
> PATA are separated into different procedures.
>
> * pdc_cable_type() is split into a PATA version and a
> SATA version
> * pdc_error_handler() is split into a PATA version and a
> SATA version, that both call a common version after
> setting up the `hardreset' function pointer
> * pdc_old_check_atapi_dma() is now only used for SATAI
> ports, so is renamed to pdc_old_sata_check_atapi_dma()
> and simplified
> * pdc_sata_scr_{read,write}() are now only used for SATA
> ports, so their is-not-SATA tests are removed
> * pdc_port_start() is split into three procedures: a wrapper
> which performs the ->ops adjustment on TX2plus PATA ports,
> a procedure with the common code, and a procedure with
> the SATA-specific code (this bit might be cleaned up by
> Tejun's new init model)
Acked-by: Tejun Heo <htejun@gmail.com>
--
tejun
prev parent reply other threads:[~2007-03-12 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 20:20 [PATCH libata#upstream 2/2] sata_promise: separate SATA and PATA ops Mikael Pettersson
2007-03-12 9:20 ` Tejun Heo [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=45F51B55.1050202@gmail.com \
--to=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).