public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH fix for 3.17 v5] uas: Add a quirk for rejecting ATA_12 and ATA_16 commands
Date: Mon, 15 Sep 2014 16:13:52 +0200	[thread overview]
Message-ID: <5416F420.9080901@redhat.com> (raw)
In-Reply-To: <20140915140807.GA26412@kroah.com>

Hi,

On 09/15/2014 04:08 PM, Greg Kroah-Hartman wrote:
> On Mon, Sep 15, 2014 at 04:04:12PM +0200, Hans de Goede wrote:
>> And set this quirk for the Seagate Expansion Desk (0bc2:2312), as that one
>> seems to hang upon receiving an ATA_12 or ATA_16 command.
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=79511
>> https://bbs.archlinux.org/viewtopic.php?id=183190
>>
>> While at it also add missing documentation for the u value for usb-storage
>> quirks.
>>
>> Cc: stable@vger.kernel.org # 3.16
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>>
>> --
>> Changes in v2: Add documentation for new t and u usb-storage.quirks flags
>> Changes in v3: Fix typo in documentation
>> Changes in v4: Also apply the quirk to (0bc2:3312)
>> Changes in v5: Rebased on 3.17-rc5, drop u documentation, already upstream
> 
> So I should wait another day for v6?  :)

Hehe, no I certainly hope not.

Chances are I there will eventually be more seagate models needing the quirk,
but I've none in the pipeline atm, and we can always add those with an
incremental patch.

So if this is not too late for 3.17 and you can pick up v5 that would be great.

Thanks,

Hans

  reply	other threads:[~2014-09-15 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 14:04 [PATCH fix for 3.17 v5] uas: Add a quirk for rejecting ATA_12 and ATA_16 commands Hans de Goede
2014-09-15 14:08 ` Greg Kroah-Hartman
2014-09-15 14:13   ` Hans de Goede [this message]
2014-09-24  4:39     ` Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5416F420.9080901@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox