From: Hannes Reinecke <hare@suse.de>
To: Maurizio Lombardi <mlombard@redhat.com>, Christoph Hellwig <hch@lst.de>
Cc: linux-scsi@vger.kernel.org, JBottomley@Parallels.com
Subject: Re: [PATCH] scsi: replace numeric messages with string error messages when blk_execute_rq fails. Also add printing of sense info.
Date: Wed, 04 Jun 2014 09:53:10 +0200 [thread overview]
Message-ID: <538ED066.7010604@suse.de> (raw)
In-Reply-To: <20140604075122.GA5700@dhcp-27-189.brq.redhat.com>
On 06/04/2014 09:51 AM, Maurizio Lombardi wrote:
> On Thu, May 15, 2014 at 08:41:10AM +0200, Christoph Hellwig wrote:
>>
>> We now have a readily available copy of EVPD page 0x83 hanging off
>> the scsi device, so the alua device handler should use it.
>>
>> Hannes, how about you handle that if you're doing major surgery in that
>> area anwyay?
>
> Hannes?
>
> Did you notice this email?
>
Oh, yes, I did.
Will be sending a patch shortly.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-06-04 7:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 11:44 [PATCH] scsi: replace numeric messages with string error messages when blk_execute_rq fails. Also add printing of sense info Maurizio Lombardi
2014-04-25 13:12 ` Christoph Hellwig
2014-04-25 15:40 ` Maurizio Lombardi
2014-04-29 9:30 ` Maurizio Lombardi
2014-04-29 18:00 ` Christoph Hellwig
2014-05-13 13:10 ` Maurizio Lombardi
2014-05-13 14:07 ` Christoph Hellwig
2014-05-13 14:14 ` Hannes Reinecke
2014-05-13 14:24 ` Maurizio Lombardi
2014-05-15 6:41 ` Christoph Hellwig
2014-06-04 7:51 ` Maurizio Lombardi
2014-06-04 7:53 ` Hannes Reinecke [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=538ED066.7010604@suse.de \
--to=hare@suse.de \
--cc=JBottomley@Parallels.com \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=mlombard@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.