Skip to content

libata: Support SATA attached via SAS

Brian King linux-ide linux-scsi 1 version Applied

Status from this message: applied

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 2 repliesApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/4libata: Conditionally set host->max_cmd_lendrivers/scsi/libata-core.c+15 -61 reply
2/4libata: Add ata_host_set_initdrivers/scsi/libata-core.c include/linux/libata.h+26 -40 replies
3/4libata: Add support for SATA attachment to SAS adaptersdrivers/scsi/libata-core.c drivers/scsi/libata-scsi.c drivers/scsi/libata.h +1 more+179 -20 replies
4/4libata: Check per device max cdb length for SASdrivers/scsi/libata-scsi.c+7 -31 reply

Reviews trailers per patch

1 of 4 patches has a Reviewed-by or Acked-by.

PatchJeff Garzik
1/4
2/4
3/4A-b
4/4

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/4] libata: Support SATA attached via SAS

Jeff,

Here are the remaining patches to my patchset to allow SAS HBAs to use libata to control attached SATA devices. You had two concerns in the last round of patches, which I have tried to address here.

1. Per device max command length checking
- You were concerned with adding an additional check to the hot path. To address this I moved the check so that it is now only made for SAS users, which is really the only users that need it since existing SATA users have host->max_cmd_len protecting them.

2. Add ata_host_flags
- You thought there might be a need to carry some cross port state. To resolve this I added a new API: ata_host_set_init. Callers of ata_sas_port_alloc must now pass their host_set pointer as the first argument. This removes the need for the patch you objected to and allows for a cross port state if needed.

Signature · 3 lines
Brian King
eServer Storage I/O
IBM Linux Technology Center