From: Hans de Goede <hdegoede@redhat.com>
To: David Laight <David.Laight@ACULAB.COM>,
'Alan Stern' <stern@rowland.harvard.edu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH fix for 3.17] uas: Add a quirk for rejecting ATA_12 and ATA_16 commands
Date: Mon, 15 Sep 2014 15:21:56 +0200 [thread overview]
Message-ID: <5416E7F4.7040604@redhat.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D17491F5F@AcuExch.aculab.com>
Hi,
On 09/15/2014 10:42 AM, David Laight wrote:
> From: Alan Stern
> ...
>>> p = quirks;
>>> while (*p) {
>>> @@ -543,6 +544,9 @@ void usb_stor_adjust_quirks(struct usb_device *udev, unsigned long *fflags)
>>> case 's':
>>> f |= US_FL_SINGLE_LUN;
>>> break;
>>> + case 't':
>>> + f |= US_FL_NO_ATA_1X;
>>> + break;
>>> case 'u':
>>> f |= US_FL_IGNORE_UAS;
>>> break;
>>
>> You must not add an aditional value for a module parameter without
>> documenting it in Documentation/kernel-parameters.txt.
>
> How can this work as a 'module parameter'?
> I might want to use two different usb-scsi devices that have different
> requirements.
The usb-storage.quirks format includes a usb prod:vend if pair, so unless
you've 2 identical devices, you can specify which quirks to apply to
which device.
Regards,
Hans
prev parent reply other threads:[~2014-09-15 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 10:19 [PATCH fix for 3.17 0/1] uas: Add a quirk for rejecting ATA_12 and ATA_16 Hans de Goede
2014-09-13 10:19 ` [PATCH fix for 3.17] uas: Add a quirk for rejecting ATA_12 and ATA_16 commands Hans de Goede
2014-09-13 14:11 ` Alan Stern
2014-09-15 8:42 ` David Laight
2014-09-15 11:12 ` Oliver Neukum
2014-09-15 14:56 ` Alan Stern
2014-09-15 13:21 ` Hans de Goede [this message]
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=5416E7F4.7040604@redhat.com \
--to=hdegoede@redhat.com \
--cc=David.Laight@ACULAB.COM \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox