From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Knibbs <mark_k@iname.com>
Cc: linux-usb@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>
Subject: [v3] storage: Widen bcdDevice range for SanDisk SDDR-31 quirk
Date: Mon, 11 Jun 2018 09:08:22 +0200 [thread overview]
Message-ID: <20180611070822.GA9472@kroah.com> (raw)
On Sun, Jun 10, 2018 at 08:54:09PM +0200, Mark Knibbs wrote:
> When I re-sent the patch with tabs I accidentally left the new maximum
> bcdDevice at 0x00ff. Sorry! Hopefully this is finally OK.
This should not be in the change log text, please remove it.
>
>
> The SanDisk SDDR-31 needs the US_FL_FIX_CAPACITY quirk. Previously that
> was only applied for bcdDevice 0x0009, but later firmware which reports
> bcdDevice 0x0022 needs it too.
>
> Signed-off-by: Mark Knibbs <mark_k@iname.com>
> ---
> diff --git a/drivers/usb/storage/unusual_devs.h b/drivers/usb/storage/unusual_devs.h
> index 747d3a9..dfcceaf 100644
Below the --- line you should put what changed for each version of the
patch, so we have an idea of what to look for when reviewing it.
> --- a/drivers/usb/storage/unusual_devs.h
> +++ b/drivers/usb/storage/unusual_devs.h
> @@ -1044,7 +1044,7 @@ UNUSUAL_DEV( 0x0781, 0x0001, 0x0200, 0x0200,
> USB_SC_SCSI, USB_PR_CB, NULL,
> US_FL_SINGLE_LUN ),
Tabs all worked fine here.
thanks,
greg k-h
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-06-11 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 7:08 Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-13 13:08 [v3] storage: Widen bcdDevice range for SanDisk SDDR-31 quirk Mark Knibbs
2018-06-10 18:54 Mark Knibbs
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=20180611070822.GA9472@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark_k@iname.com \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.