From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Saurav Girepunje <saurav.girepunje@gmail.com>
Cc: james.smart@broadcom.com, dick.kennedy@broadcom.com,
jejb@linux.ibm.com, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
saurav.girepunje@hotmail.com, saurav.girepunje@gmail.com
Subject: Re: [PATCH] scsi: lpfc: Fix NULL check before mempool_destroy is not needed
Date: Mon, 28 Oct 2019 21:53:22 -0400 [thread overview]
Message-ID: <yq1lft48gh9.fsf@oracle.com> (raw)
In-Reply-To: <20191026194712.GA22249@saurav> (Saurav Girepunje's message of "Sun, 27 Oct 2019 01:17:17 +0530")
Saurav,
> mempool_destroy has taken null pointer check into account. so remove
> the redundant check.
Applied to 5.5/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-10-29 1:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191026194712.GA22249@saurav>
2019-10-28 17:42 ` [PATCH] scsi: lpfc: Fix NULL check before mempool_destroy is not needed James Smart
2019-10-29 1:53 ` Martin K. Petersen [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=yq1lft48gh9.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=dick.kennedy@broadcom.com \
--cc=james.smart@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=saurav.girepunje@gmail.com \
--cc=saurav.girepunje@hotmail.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