This is a note to let you know that I've just added the patch titled
uas: Add US_FL_NO_ATA_1X quirk for Seagate (0bc2:ab20) drives
to the 3.17-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
uas-add-us_fl_no_ata_1x-quirk-for-seagate-0bc2-ab20-drives.patch
and it can be found in the queue-3.17 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From f9554a6b199360c2f888173fd600e1eb7ff165ef Mon Sep 17 00:00:00 2001
From: Hans de Goede <hdegoede@xxxxxxxxxx>
Date: Wed, 17 Sep 2014 10:10:58 +0200
Subject: uas: Add US_FL_NO_ATA_1X quirk for Seagate (0bc2:ab20) drives
From: Hans de Goede <hdegoede@xxxxxxxxxx>
commit f9554a6b199360c2f888173fd600e1eb7ff165ef upstream.
https://bbs.archlinux.org/viewtopic.php?pid=1457492
Signed-off-by: Hans de Goede <hdegoede@xxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/usb/storage/unusual_uas.h | 7 +++++++
1 file changed, 7 insertions(+)
--- a/drivers/usb/storage/unusual_uas.h
+++ b/drivers/usb/storage/unusual_uas.h
@@ -54,6 +54,13 @@ UNUSUAL_DEV(0x0bc2, 0x3312, 0x0000, 0x99
USB_SC_DEVICE, USB_PR_DEVICE, NULL,
US_FL_NO_ATA_1X),
+/* https://bbs.archlinux.org/viewtopic.php?id=183190 */
+UNUSUAL_DEV(0x0bc2, 0xab20, 0x0000, 0x9999,
+ "Seagate",
+ "Backup+ BK",
+ USB_SC_DEVICE, USB_PR_DEVICE, NULL,
+ US_FL_NO_ATA_1X),
+
/* Reported-by: Claudio Bizzarri <claudio.bizzarri@xxxxxxxxx> */
UNUSUAL_DEV(0x152d, 0x0567, 0x0000, 0x9999,
"JMicron",
Patches currently in stable-queue which might be from hdegoede@xxxxxxxxxx are
queue-3.17/uas-add-us_fl_no_ata_1x-quirk-for-seagate-0bc2-ab20-drives.patch
queue-3.17/uas-add-another-asm1051-usb-id-to-the-uas-blacklist.patch
queue-3.17/uas-add-no-report-opcodes-quirk.patch
queue-3.17/uas-add-a-quirk-for-rejecting-ata_12-and-ata_16-commands.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html