Re: [PATCH RESEND] lpfc: Don't return internal MBXERR_ERROR code from probe function

To: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>, Stefano Brivio <sbrivio@xxxxxxxxxx>
Subject: Re: [PATCH RESEND] lpfc: Don't return internal MBXERR_ERROR code from probe function
From: James Smart <james.smart@xxxxxxxxxxxx>
Date: Fri, 15 Sep 2017 07:18:10 -0700
Cc: Dick Kennedy <dick.kennedy@xxxxxxxxxxxx>, QLogic-Storage-Upstream@xxxxxxxxxx, Maurizio Lombardi <mlombard@xxxxxxxxxx>, "James E . J . Bottomley" <jejb@xxxxxxxxxxxxxxxxxx>, linux-scsi@xxxxxxxxxxxxxxx, Johannes Thumshirn <jthumshirn@xxxxxxx>
In-reply-to: <yq1k210rc66.fsf@oracle.com>
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0

On 9/14/2017 6:19 PM, Martin K. Petersen wrote:

James/Dick,

Please review!


It seemed to be changing so I was waiting for the final posting...

-- james

References:
- [PATCH] lpfc: Don't return internal MBXERR_ERROR code from probe function
  - From: Stefano Brivio
- [PATCH RESEND] lpfc: Don't return internal MBXERR_ERROR code from probe function
  - From: Stefano Brivio
- Re: [PATCH RESEND] lpfc: Don't return internal MBXERR_ERROR code from probe function
  - From: Martin K. Petersen