From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
"James E.J. Bottomley" <JBottomley@parallels.com>,
Matthew Dharm <mdharm-usb@one-eyed-alien.net>,
linux-scsi@vger.kernel.org, usb-storage@lists.one-eyed-alien.net,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] scsi: usb-storage: hide errors for five devices
Date: Tue, 22 May 2012 10:25:55 +0100 [thread overview]
Message-ID: <20120522102555.3830d0bd@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <1337676514.7898.8.camel@x61.thuisdomein>
On Tue, 22 May 2012 10:48:34 +0200
Paul Bolle <pebolle@tiscali.nl> wrote:
> On Tue, 2012-05-15 at 17:36 +0100, Alan Cox wrote:
> > Possibly we should have a hostadapter flag indicating if the cache noise
> > is expected nuisance or not. That way if hardcore SCSI on real cables
> > wants to keeep it then it can still be shut up for USB where its the
> > norm and just irrelevant noise.
>
> 0) Nobody suggested anything else so maybe I should try to come up with
> a patch that does that. A slight problem is that I'm not at all familiar
> with the SCSI code. And I don't think I own any actual SCSI hardware.
Give it a go.. only one way to learn 8)
> 1) Anyhow: hostadapter flags? Are those perhaps the bitfields starting
> with "active_mode" in "struct Scsi_Host"?
It can probably go in the scsi_host_template. It's going to be per
adapter and fixed. It will still be accessible then via
host->hostt->whatever. That also makes it easier to set correctly.
Alan
prev parent reply other threads:[~2012-05-22 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 10:19 [PATCH 0/3] scsi: usb-storage: hide errors for five devices Paul Bolle
2012-05-08 14:02 ` Alan Stern
2012-05-08 15:37 ` Paul Bolle
2012-05-08 17:03 ` Alan Stern
2012-05-15 15:35 ` Greg Kroah-Hartman
2012-05-15 16:29 ` Paul Bolle
2012-05-15 16:36 ` Alan Cox
2012-05-22 8:48 ` Paul Bolle
2012-05-22 9:25 ` Alan Cox [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=20120522102555.3830d0bd@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=JBottomley@parallels.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=pebolle@tiscali.nl \
--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