From: Jeremy Linton <jlinton@tributary.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Elliott, Robert (Server Storage)" <Elliott@hp.com>,
Rob Evers <revers@redhat.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"michaelc@cs.wisc.edu" <michaelc@cs.wisc.edu>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"emilne@redhat.com" <emilne@redhat.com>
Subject: Re: [PATCH V3 1/4] Encapsulate scsi_do_report_luns
Date: Thu, 7 Mar 2013 11:42:24 -0600 [thread overview]
Message-ID: <5138D180.4010909@tributary.com> (raw)
In-Reply-To: <1362677438.9043.6.camel@dabdike.int.hansenpartnership.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 3/7/2013 11:30 AM, James Bottomley wrote:
> This also means we can't go through the linux SCSI subsystem changing
> behaviour based on what SAM says the behaviour should be. Most of what the
> SCSI subsystem does is an accumulation based on years of trying to fix it
> for annoying and out of spec devices.
Well, I wasn't suggesting removing the retries for this patch, cause yes
there are a lot of non complaint devices, but I was complaining about a case
where there are known problems with the way the code is executing on non
broken devices.
Basically, prioritizing the functionality of a broken device, of the
functionality of a working one.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRONGAAAoJEL5i86xrzcy7a6QH/16EQyMQ3DzLrX2a3OdtSD4Q
QdHInok1SAyGKDGHTHXGu0RKuvpzgdSLjORKfEdbok/ZyNXd7qSi57czRV7R5U4b
nTLoaP8maXxJsJ1ko11sTEfZNT4cgO4+hLMjcZk9LBJZhNC+WqsszYaOVVLFtSIJ
xpBaowSjxLpkhi5cTdZ6p4+Tr2xgZxBXd+5NUZuB1s6ZJ99yNYcn97Q/3VVeFmW9
sprBP3kkiWv3LOIN6ZNTkKRDtgJYzf2LVTogjtNfCQsB/ZUHr5ITzZ1fMBkVrR7c
yVe4kdq26RDC57oSJMqAHA8QXBQ2ll8l8fz1X1mebb2TeyOI57/U8ZbPyfGvzxo=
=yZvD
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-03-07 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 13:38 [PATCH V3 0/4] Configure number of LUs reported by 'report-luns' Rob Evers
2013-03-07 13:38 ` [PATCH V3 1/4] Encapsulate scsi_do_report_luns Rob Evers
2013-03-07 15:47 ` Elliott, Robert (Server Storage)
2013-03-07 16:06 ` Jeremy Linton
2013-03-07 17:01 ` Elliott, Robert (Server Storage)
2013-03-07 17:30 ` James Bottomley
2013-03-07 17:38 ` Elliott, Robert (Server Storage)
2013-03-07 17:48 ` James Bottomley
2013-03-07 17:42 ` Jeremy Linton [this message]
2013-03-07 13:38 ` [PATCH V3 2/4] Configure reported luns Rob Evers
2013-03-07 13:38 ` [PATCH V3 3/4] Change kmallocs in report_luns to use GFP_KERNEL Rob Evers
2013-03-07 13:38 ` [PATCH V3 4/4] Use set/get_unaligned_be32 in report_luns Rob Evers
2013-03-07 14:31 ` [PATCH V3 0/4] Configure number of LUs reported by 'report-luns' Ewan Milne
2013-03-07 17:01 ` Rob Evers
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=5138D180.4010909@tributary.com \
--to=jlinton@tributary.com \
--cc=Elliott@hp.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--cc=emilne@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=revers@redhat.com \
/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.