The patch titled
     libata-check-for-an-support update
has been removed from the -mm tree.  Its filename was
     libata-check-for-an-support-update.patch

This patch was dropped because it was folded into 
libata-check-for-an-support.patch

------------------------------------------------------
Subject: libata-check-for-an-support update
From: Kristen Carlson Accardi <[EMAIL PROTECTED]>

Andrew, I cleaned up the function header to properly comply with kernel
doc requirements.

Signed-off-by: Kristen Carlson Accardi <[EMAIL PROTECTED]>
Cc: "Randy.Dunlap" <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 drivers/ata/libata-core.c |    5 ++---
 1 files changed, 2 insertions(+), 3 deletions(-)

diff -puN drivers/ata/libata-core.c~libata-check-for-an-support-update 
drivers/ata/libata-core.c
--- a/drivers/ata/libata-core.c~libata-check-for-an-support-update
+++ a/drivers/ata/libata-core.c
@@ -3915,12 +3915,11 @@ static unsigned int ata_dev_set_xfermode
 
 /**
  *     ata_dev_set_AN - Issue SET FEATURES - SATA FEATURES
- *                       with sector count set to indicate
- *                       Asynchronous Notification feature
  *     @dev: Device to which command will be sent
  *
  *     Issue SET FEATURES - SATA FEATURES command to device @dev
- *     on port @ap.
+ *     on port @ap with sector count set to indicate Asynchronous
+ *     Notification feature
  *
  *     LOCKING:
  *     PCI/etc. bus probe sem.
_

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

origin.patch
git-acpi.patch
libata-check-for-an-support.patch
libata-check-for-an-support-update.patch
genhd-expose-an-to-user-space.patch
scsi-expose-an-to-user-space.patch
libata-expose-an-to-user-space.patch
genhd-send-async-notification-on-media-change.patch
scsi-save-disk-in-scsi_device.patch
libata-send-event-when-an-received.patch
cpci_hotplug-convert-to-use-the-kthread-api.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