From: Oliver Neukum <oneukum@suse.com>
To: Alan Stern <stern@rowland.harvard.edu>,
Alexander Kappner <agk@godking.net>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
usb-storage@lists.one-eyed-alien.net, gregkh@linuxfoundation.org
Subject: usb-storage: Add quirks to make G-Technology "G-Drive" work
Date: Tue, 22 May 2018 10:57:12 +0200 [thread overview]
Message-ID: <1526979432.30491.0.camel@suse.com> (raw)
Am Montag, den 21.05.2018, 13:47 -0400 schrieb Alan Stern:
> On Fri, 18 May 2018, Alexander Kappner wrote:
>
> > v2 of this patch implements the FL_ALWAYS_SYNC flag in the UAS driver, and then
> > adds the flag as quirks for the device at issue. This allows the G-Drive to work
> > under both UAS and usb-storage.
> >
> > Alexander Kappner (2):
> > [usb-storage] Add support for FL_ALWAYS_SYNC flag in the UAS driver
> > [usb-storage] Add compatibility quirk flags for G-Technologies G-Drive
> >
> > drivers/usb/storage/uas.c | 6 ++++++
> > drivers/usb/storage/unusual_devs.h | 9 +++++++++
> > drivers/usb/storage/unusual_uas.h | 9 +++++++++
> > 3 files changed, 24 insertions(+)
>
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
>
> This is okay with me. Oliver, what do you think?
Perfect.
Regards
Oliver
---
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-05-22 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 8:57 Oliver Neukum [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-21 17:47 usb-storage: Add quirks to make G-Technology "G-Drive" work Alan Stern
2018-05-19 4:50 Alexander Kappner
2018-05-18 20:35 Alan Stern
2018-05-18 17:51 Alexander Kappner
2018-05-17 19:13 Alan Stern
2018-05-17 18:38 Alexander Kappner
2018-05-17 14:44 Alan Stern
2018-05-17 12:58 Oliver Neukum
2018-05-17 8:15 Alexander Kappner
2018-05-16 20:55 Alan Stern
2018-05-16 20:01 Alexander Kappner
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=1526979432.30491.0.camel@suse.com \
--to=oneukum@suse.com \
--cc=agk@godking.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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;
as well as URLs for NNTP newsgroup(s).