From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: YueHaibing <yuehaibing@huawei.com>
Cc: QLogic-Storage-Upstream@qlogic.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH -next] scsi: qla4xxx: check return code of qla4xxx_copy_from_fwddb_param
Date: Fri, 04 Jan 2019 01:04:37 -0500 [thread overview]
Message-ID: <yq1ef9t6jre.fsf@oracle.com> (raw)
In-Reply-To: <20181220031607.10588-1-yuehaibing@huawei.com> (YueHaibing's message of "Thu, 20 Dec 2018 11:16:07 +0800")
YueHaibing,
> The return code should be check while qla4xxx_copy_from_fwddb_param
> fails.
Applied to 4.21/scsi-fixes, thank you.
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: YueHaibing <yuehaibing@huawei.com>
Cc: <QLogic-Storage-Upstream@qlogic.com>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>, <linux-kernel@vger.kernel.org>,
<linux-scsi@vger.kernel.org>
Subject: Re: [PATCH -next] scsi: qla4xxx: check return code of qla4xxx_copy_from_fwddb_param
Date: Fri, 04 Jan 2019 01:04:37 -0500 [thread overview]
Message-ID: <yq1ef9t6jre.fsf@oracle.com> (raw)
In-Reply-To: <20181220031607.10588-1-yuehaibing@huawei.com> (YueHaibing's message of "Thu, 20 Dec 2018 11:16:07 +0800")
YueHaibing,
> The return code should be check while qla4xxx_copy_from_fwddb_param
> fails.
Applied to 4.21/scsi-fixes, thank you.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-01-04 6:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 3:16 [PATCH -next] scsi: qla4xxx: check return code of qla4xxx_copy_from_fwddb_param YueHaibing
2018-12-20 3:16 ` YueHaibing
2018-12-24 8:49 ` [EXT] " Manish Rangankar
2019-01-04 6:04 ` Martin K. Petersen [this message]
2019-01-04 6:04 ` Martin K. Petersen
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=yq1ef9t6jre.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=QLogic-Storage-Upstream@qlogic.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=yuehaibing@huawei.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.