From: Oliver Neukum <oneukum@suse.com>
To: Hans de Goede <hdegoede@redhat.com>,
Alan Stern <stern@rowland.harvard.edu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-scsi@vger.kernel.org, linux-usb@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] uas: Add US_FL_NO_ATA_1X quirk for one more Seagate device
Date: Wed, 15 Nov 2017 10:06:58 +0100 [thread overview]
Message-ID: <1510736818.5412.2.camel@suse.com> (raw)
In-Reply-To: <c03f33ff-81e8-1753-f648-94c107e994ad@redhat.com>
Am Dienstag, den 14.11.2017, 18:44 +0100 schrieb Hans de Goede:
>
> Greg, please do no merge the 2 recent uas seagate quirks I send
> then. I will submit a patch with the new approach right away.
Hi,
I am afraid in that case we will need a way to override a
quirk in the other direction, that is, to not apply it.
Regards
Oliver
next prev parent reply other threads:[~2017-11-15 9:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 14:00 [PATCH] uas: Add US_FL_NO_ATA_1X quirk for one more Seagate device Hans de Goede
2017-11-14 14:00 ` Hans de Goede
[not found] ` <20171114140017.17782-1-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-14 14:04 ` Hans de Goede
2017-11-14 14:04 ` Hans de Goede
2017-11-14 15:25 ` Alan Stern
2017-11-14 15:25 ` Alan Stern
2017-11-14 17:44 ` Hans de Goede
2017-11-15 9:06 ` Oliver Neukum [this message]
2017-11-15 9:32 ` Hans de Goede
-- strict thread matches above, loose matches on Subject: below --
2017-11-10 15:13 Hans de Goede
2017-11-12 21:42 ` Jérôme Carretero
[not found] ` <20171112164234.48b5185c-WI5o+PA4G9BYumZHjSPV5A@public.gmane.org>
2017-11-13 4:01 ` Andrey Astafyev
2017-11-13 6:14 ` Jérôme Carretero
2017-11-13 6:16 ` Andrey Astafyev
2017-11-13 7:14 ` Jérôme Carretero
[not found] ` <20171113011438.458369bf-WI5o+PA4G9BYumZHjSPV5A@public.gmane.org>
2017-11-13 9:04 ` Hans de Goede
[not found] ` <3d276729-63f7-9727-4a22-55849712439c-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-13 17:38 ` Jérôme Carretero
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=1510736818.5412.2.camel@suse.com \
--to=oneukum@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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.