Re: kernel 5.0 blk_clear_pm_only triggers a warning during resume

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

To: Jisheng Zhang <Jisheng.Zhang@xxxxxxxxxxxxx>
Subject: Re: kernel 5.0 blk_clear_pm_only triggers a warning during resume
From: Bart Van Assche <bvanassche@xxxxxxx>
Date: Fri, 15 Mar 2019 16:07:02 -0700
Cc: "James E.J. Bottomley" <jejb@xxxxxxxxxxxxx>, "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>, Jens Axboe <axboe@xxxxxxxxx>, "linux-scsi@xxxxxxxxxxxxxxx" <linux-scsi@xxxxxxxxxxxxxxx>, "linux-block@xxxxxxxxxxxxxxx" <linux-block@xxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <20190314101355.1df7c014@xhacker.debian>

On Thu, 2019-03-14 at 02:21 +-0000, Jisheng Zhang wrote:
+AD4 Good news. The patch fix the warning. So 
+AD4 
+AD4 Tested-by: Jisheng Zhang +ADw-Jisheng.Zhang+AEA-synaptics.com+AD4

Thank you for having tested my patch+ACE

Bart.

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

References:
- kernel 5.0 blk_clear_pm_only triggers a warning during resume
  - From: Jisheng Zhang
- Re: kernel 5.0 blk_clear_pm_only triggers a warning during resume
  - From: Bart Van Assche
- Re: kernel 5.0 blk_clear_pm_only triggers a warning during resume
  - From: Jisheng Zhang
- Re: kernel 5.0 blk_clear_pm_only triggers a warning during resume
  - From: Jisheng Zhang

Prev by Date: [PATCH 2/2] qla2xxx: Fix NULL pointer crash due to stale CPUID
Next by Date: Re: [PATCH v5 5/7] dt-bindings: scsi: ufs: Add document for ufs-mediatek
Previous by thread: Re: kernel 5.0 blk_clear_pm_only triggers a warning during resume
Next by thread: [PATCH] simscsi: use request tag instead of serial_number
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]