From: James Smart <jsmart2021@gmail.com>
To: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>,
linux-nvme@lists.infradead.org
Cc: Dick Kennedy <dick.kennedy@broadcom.com>,
James Smart <james.smart@broadcom.com>,
raphasil@linux.vnet.ibm.com,
Linux SCSI Mailinglist <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v2 02/15] lpfc: Fix system crash when port is reset.
Date: Wed, 17 May 2017 11:49:10 -0700 [thread overview]
Message-ID: <c2bf3df0-e65e-2f1c-5bb7-cb5b62697e30@gmail.com> (raw)
In-Reply-To: <73cdc776-8eea-b63b-89af-ffa9829e1f9d@linux.vnet.ibm.com>
On 5/16/2017 5:26 AM, Guilherme G. Piccoli wrote:
> On 05/15/2017 07:20 PM, James Smart wrote:
>> The driver panic when using the els_wq during port reset.
>>
>> Check for NULL els_wq before dereferencing.
>
> James/Dick, if possible please take a look on:
> https://marc.info/?l=linux-scsi&m=149487670315697
>
> For some reason that email didn't get threaded as I expect. And also I
> forgot to include James' Gmail address, sorry.
>
> Thanks in advance,
>
>
> Guilherme
Gilherme,
Your patch is still needed. Can you repost your patch with a new
subject and add my signature:
Signed-off-by: James Smart <james.smart@broadcom.com>
Sorry, I didn't see it to roll it into the set.
-- james
next parent reply other threads:[~2017-05-17 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170515222052.26004-1-jsmart2021@gmail.com>
[not found] ` <20170515222052.26004-3-jsmart2021@gmail.com>
[not found] ` <73cdc776-8eea-b63b-89af-ffa9829e1f9d@linux.vnet.ibm.com>
2017-05-17 18:49 ` James Smart [this message]
2017-05-17 22:06 ` [PATCH v2 02/15] lpfc: Fix system crash when port is reset Guilherme G. Piccoli
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=c2bf3df0-e65e-2f1c-5bb7-cb5b62697e30@gmail.com \
--to=jsmart2021@gmail.com \
--cc=dick.kennedy@broadcom.com \
--cc=gpiccoli@linux.vnet.ibm.com \
--cc=james.smart@broadcom.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=raphasil@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox