The patch titled
     libata: relocate sdev->manage_start_stop configuration
has been removed from the -mm tree.  Its filename was
     libata-relocate-sdev-manage_start_stop-configuration.patch

This patch was dropped because it was merged into mainline or a subsystem tree

The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
Subject: libata: relocate sdev->manage_start_stop configuration
From: Tejun Heo <[EMAIL PROTECTED]>

After 9b8e8de7, manage_start_stop configuration depends on valid ATA
device.  Move it into ata_scsi_dev_config().  This was detected by the
coverity checker.

Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Cc: Adrian Bunk <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 drivers/ata/libata-scsi.c |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff -puN 
drivers/ata/libata-scsi.c~libata-relocate-sdev-manage_start_stop-configuration 
drivers/ata/libata-scsi.c
--- 
a/drivers/ata/libata-scsi.c~libata-relocate-sdev-manage_start_stop-configuration
+++ a/drivers/ata/libata-scsi.c
@@ -841,6 +841,9 @@ static void ata_scsi_dev_config(struct s
                blk_queue_max_hw_segments(q, q->max_hw_segments - 1);
        }
 
+       if (dev->class == ATA_DEV_ATA)
+               sdev->manage_start_stop = 1;
+
        if (dev->flags & ATA_DFLAG_AN)
                set_bit(SDEV_EVT_MEDIA_CHANGE, sdev->supported_events);
 
@@ -872,9 +875,6 @@ int ata_scsi_slave_config(struct scsi_de
 
        ata_scsi_sdev_config(sdev);
 
-       if (dev->class == ATA_DEV_ATA)
-               sdev->manage_start_stop = 1;
-
        if (dev)
                ata_scsi_dev_config(sdev, dev);
 
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

origin.patch
git-kbuild.patch
git-libata-all.patch
pata_legacy-resychronize-with-upstream-changes-and-resubmit.patch
git-scsi-misc.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to