Re: [PATCH v2] scsi: pm8001: Fix bogus FW crash for maxcpus=1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: John Garry <john.garry@xxxxxxxxxx>
Subject: Re: [PATCH v2] scsi: pm8001: Fix bogus FW crash for maxcpus=1
From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
Date: Tue, 18 Jan 2022 22:41:02 -0500
Cc: <jinpu.wang@xxxxxxxxxxxxxxx>, <jejb@xxxxxxxxxxxxx>, <martin.petersen@xxxxxxxxxx>, <damien.lemoal@xxxxxxxxxxxxxxxxxx>, <Ajish.Koshy@xxxxxxxxxxxxx>, <linux-scsi@xxxxxxxxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>, <Viswas.G@xxxxxxxxxxxxx>, <vishakhavc@xxxxxxxxxx>, <ipylypiv@xxxxxxxxxx>, <Ruksar.devadi@xxxxxxxxxxxxx>, <Vasanthalakshmi.Tharmarajan@xxxxxxxxxxxxx>
In-reply-to: <1642508105-95432-1-git-send-email-john.garry@huawei.com> (John Garry's message of "Tue, 18 Jan 2022 20:15:05 +0800")
Organization: Oracle Corporation

John,

> According to the comment in check_fw_ready() we should not check the
> IOP1_READY field in register SCRATCH_PAD_1 for 8008 or 8009
> controllers.

Applied to 5.17/scsi-staging, thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- [PATCH v2] scsi: pm8001: Fix bogus FW crash for maxcpus=1
  - From: John Garry

Prev by Date: Re: [PATCH 0/3] qedf misc bug fixes
Next by Date: Re: [PATCH] zfcp: fix failed recovery on gone remote port with non-NPIV FCP devices
Previous by thread: [PATCH v2] scsi: pm8001: Fix bogus FW crash for maxcpus=1
Next by thread: Re: [PATCH v2] scsi: pm8001: Fix bogus FW crash for maxcpus=1
Index(es):
- Date
- Thread

[Index of Archives] [SCSI Target Devel] [Linux SCSI Target Infrastructure] [Kernel Newbies] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Linux IIO] [Samba] [Device Mapper]

Powered by Linux