From: Tejun Heo <htejun@gmail.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: jeff@garzik.org, linux-ide@vger.kernel.org
Subject: Re: [PATCHSET] libata: implement ata_link, take 6
Date: Mon, 06 Aug 2007 15:12:06 +0900 [thread overview]
Message-ID: <46B6BBB6.4020600@gmail.com> (raw)
In-Reply-To: <1186232650.3439.1.camel@localhost.localdomain>
James Bottomley wrote:
> On Sat, 2007-08-04 at 17:42 +0900, Tejun Heo wrote:
>> This is the sixth take of implement ata_link patchset. This patchset
>> contains 14 patches which can be categorized as follows.
>>
>> #01-02: implement ata_link
>> #03-06: make libata deal with link instead of port
>> #07-09: misc link stuff (link init, reset_tries, ata_link_abort())
>> #10-14: add ap->pmp_link[] and update libata to deal with multiple
>> links
>>
>> ata_link abstracts PHY and sits between ata_port and ata_device. The
>> following attributes are moved to ata_link from ata_port.
>>
>> - active command state (active_tag, sactive)
>> - [hw_]sata_spd_limit
>> - eh_info and eh_context
>> - device array
>>
>> With above and a few extra fields, a link can handle attached devices
>> including qc management and EH/hotplug. This patchset makes libata
>> ready to handle PMP links.
>>
>> Changes from the last take[L] are.
>>
>> * adapted to the current upstream
>>
>> This patchset is against
>>
>> libata-dev#upstream (80c51b13d8a73b9346ebe849cdeac6f539066fc2)
>
> Sorry; there's another piece now: libsas: drivers/scsi/libsas/sas_ata.c
> will need similar treatment to ipr.
Ah... right. Sorry about that. Will regenerate the patchset.
--
tejun
prev parent reply other threads:[~2007-08-06 6:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 8:42 [PATCHSET] libata: implement ata_link, take 6 Tejun Heo
2007-08-04 8:42 ` [PATCH 03/14] libata-link: linkify PHY-related functions Tejun Heo
2007-08-04 8:42 ` [PATCH 05/14] libata-link: linkify reset Tejun Heo
2007-08-04 8:42 ` [PATCH 02/14] libata-link: implement and use link/device iterators Tejun Heo
2007-08-04 8:42 ` [PATCH 01/14] libata-link: introduce ata_link Tejun Heo
2007-08-04 8:42 ` [PATCH 04/14] libata-link: linkify EH action helpers Tejun Heo
2007-08-04 8:42 ` [PATCH 08/14] libata-link: separate out link initialization functions Tejun Heo
2007-08-04 8:42 ` [PATCH 06/14] libata-link: linkify config/EH related functions Tejun Heo
2007-08-04 8:42 ` [PATCH 10/14] libata-link: add PMP links Tejun Heo
2007-08-04 8:42 ` [PATCH 07/14] libata-link: make two port flags HRST_TO_RESUME and SKIP_D2H_BSY link flags Tejun Heo
2007-08-04 8:42 ` [PATCH 09/14] libata-link: implement ata_link_abort() Tejun Heo
2007-08-04 8:42 ` [PATCH 14/14] libata-link: update Power Management to handle PMP links Tejun Heo
2007-08-04 8:42 ` [PATCH 13/14] libata-link: update hotplug " Tejun Heo
2007-08-04 8:42 ` [PATCH 12/14] libata-link: update EH to deal with " Tejun Heo
2007-08-04 8:42 ` [PATCH 11/14] libata-link: update ata_scsi_error() to handle " Tejun Heo
2007-08-04 13:04 ` [PATCHSET] libata: implement ata_link, take 6 James Bottomley
2007-08-06 6:12 ` 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=46B6BBB6.4020600@gmail.com \
--to=htejun@gmail.com \
--cc=James.Bottomley@SteelEye.com \
--cc=jeff@garzik.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).