From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "beanhuo@micron.com" <beanhuo@micron.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"quic_nguyenb@quicinc.com" <quic_nguyenb@quicinc.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"sh8267.baek@samsung.com" <sh8267.baek@samsung.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v1 1/1] scsi: ufs : core: Add ufshcd_update_evt_hist for ufs suspend error.
Date: Wed, 10 Dec 2025 12:29:30 +0000 [thread overview]
Message-ID: <d7bc09259668d17daa0aca4b8258a2c33a643eb4.camel@mediatek.com> (raw)
In-Reply-To: <20251210063854.1483899-2-sh8267.baek@samsung.com>
On Wed, 2025-12-10 at 15:38 +0900, Seunghwan Baek wrote:
> If the ufs resume fails, the event history is updated in
> ufshcd_resume,
> but there is no code anywhere to record ufs suspend. Therefore, add
> code
> to record ufs suspend error event history.
>
> Fixes: dd11376b9f1b ("scsi: ufs: Split the drivers/scsi/ufs
> directory")
> Cc: stable@vger.kernel.org
>
> Signed-off-by: Seunghwan Baek <sh8267.baek@samsung.com>
Reviewed-by: Peter Wang <peter.wang@mediatek.com>
next prev parent reply other threads:[~2025-12-10 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20251210063900epcas1p2d70b81b127dcf2435d2028fca70ba6af@epcas1p2.samsung.com>
2025-12-10 6:38 ` [PATCH v1 0/1] Add code for ufs suspend error Seunghwan Baek
2025-12-10 6:38 ` [PATCH v1 1/1] scsi: ufs : core: Add ufshcd_update_evt_hist " Seunghwan Baek
2025-12-10 12:29 ` Peter Wang (王信友) [this message]
2025-12-17 3:40 ` 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=d7bc09259668d17daa0aca4b8258a2c33a643eb4.camel@mediatek.com \
--to=peter.wang@mediatek.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_nguyenb@quicinc.com \
--cc=sh8267.baek@samsung.com \
--cc=stable@vger.kernel.org \
/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