The patch titled pata_isapnp: put cable type back has been removed from the -mm tree. Its filename was pata_isapnp-put-cable-type-back.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ Subject: pata_isapnp: put cable type back From: Alan Cox <alan@xxxxxxxxxx> Signed-off-by: Alan Cox <alan@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/ata/pata_isapnp.c | 1 + 1 file changed, 1 insertion(+) diff -puN drivers/ata/pata_isapnp.c~pata_isapnp-put-cable-type-back drivers/ata/pata_isapnp.c --- a/drivers/ata/pata_isapnp.c~pata_isapnp-put-cable-type-back +++ a/drivers/ata/pata_isapnp.c @@ -49,6 +49,7 @@ static struct ata_port_operations isapnp .thaw = ata_bmdma_thaw, .error_handler = ata_bmdma_error_handler, .post_internal_cmd = ata_bmdma_post_internal_cmd, + .cable_detect = ata_cable_40wire, .qc_prep = ata_qc_prep, .qc_issue = ata_qc_issue_prot, _ Patches currently in -mm which might be from alan@xxxxxxxxxx are origin.patch git-libata-all.patch pcmcia-spot-slave-decode-flaws-for-testing.patch ata_generic-remove-all-the-crud-again-and-use-cable.patch pata_ali-remove-all-the-crap-again-and-switch-to.patch pata_amd-remove-all-the-crud-and-restore-the-cable-detect.patch pata_cs5535-re-remove-all-the-crap-and-switch-to-the-cable.patch pata_cypress-re-remove-all-the-crap-and-switch-back-to.patch pata_netcell-re-remove-all-the-crud.patch pata_qdi-restore-cable-detect.patch pata_sl82c105-restore-cable-detect-method.patch pata_winbond-restore-cable-method.patch libata-acpi-add-infrastructure-for-drivers-to-use.patch pata_optidma-rework-for-cable-detect-and-to-remove.patch pata_pdc2027x-restore-various-updates-done-on-the-driver.patch pata_acpi-restore-driver.patch resend-iphase-64bit-cleanup.patch pci_module_init-convertion-in-tmscsimc.patch tty-clarify-documentation-of-write.patch tty-i386-x86_64-arbitary-speed-support.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html