From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: JBottomley@Parallels.com, jejb@linux.ibm.com,
jayamohank@gmail.com, jitendra.bhivare@broadcom.com,
subbu.seetharaman@broadcom.com,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
ketan.mukadam@broadcom.com, minhduc.tran@emulex.com,
sony.john-n@emulex.com
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
kernel-janitors@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] scsi: be2iscsi: Fix an error handling path in 'beiscsi_dev_probe()'
Date: Tue, 29 Jun 2021 00:10:04 -0400 [thread overview]
Message-ID: <162493961198.16549.8268299897903445004.b4-ty@oracle.com> (raw)
In-Reply-To: <77adb02cfea7f1364e5603ecf3930d8597ae356e.1623482155.git.christophe.jaillet@wanadoo.fr>
On Sat, 12 Jun 2021 09:18:34 +0200, Christophe JAILLET wrote:
> If an error occurs after a 'pci_enable_pcie_error_reporting()' call, it
> must be undone by a corresponding 'pci_disable_pcie_error_reporting()'
> call, as already done in the remove function.
Applied to 5.14/scsi-queue, thanks!
[1/2] scsi: be2iscsi: Fix an error handling path in 'beiscsi_dev_probe()'
https://git.kernel.org/mkp/scsi/c/030e4138d11f
[2/2] scsi: be2iscsi: Fix some missing space in some messages (+some extra style issues)
https://git.kernel.org/mkp/scsi/c/c7fa2c855e89
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2021-06-29 4:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 7:18 [PATCH 1/2] scsi: be2iscsi: Fix an error handling path in 'beiscsi_dev_probe()' Christophe JAILLET
2021-06-12 7:18 ` [PATCH 2/2] scsi: be2iscsi: Fix some missing space in some messages (+some extra style issues) Christophe JAILLET
2021-06-23 2:19 ` [PATCH 1/2] scsi: be2iscsi: Fix an error handling path in 'beiscsi_dev_probe()' Martin K. Petersen
2021-06-29 4:10 ` 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=162493961198.16549.8268299897903445004.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=JBottomley@Parallels.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jayamohank@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=jitendra.bhivare@broadcom.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=ketan.mukadam@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=minhduc.tran@emulex.com \
--cc=sony.john-n@emulex.com \
--cc=subbu.seetharaman@broadcom.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;
as well as URLs for NNTP newsgroup(s).