public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"Bean Huo" <beanhuo@micron.com>,
	stable@vger.kernel.org,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	"Peter Wang" <peter.wang@mediatek.com>,
	"Avri Altman" <avri.altman@wdc.com>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	"Maramaina Naresh" <quic_mnaresh@quicinc.com>,
	"Mike Bi" <mikebi@micron.com>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	"Luca Porzio" <lporzio@micron.com>
Subject: Re: [PATCH] scsi: ufs: Start the RTC update work later
Date: Mon, 04 Nov 2024 21:31:12 -0500	[thread overview]
Message-ID: <yq1ttcm4dju.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20241031212632.2799127-1-bvanassche@acm.org> (Bart Van Assche's message of "Thu, 31 Oct 2024 14:26:24 -0700")


Bart,

> The RTC update work involves runtime resuming the UFS controller. Hence,
> only start the RTC update work after runtime power management in the UFS
> driver has been fully initialized. This patch fixes the following kernel
> crash:

Applied to 6.12/scsi-fixes, thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2024-11-05  2:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31 21:26 [PATCH] scsi: ufs: Start the RTC update work later Bart Van Assche
2024-11-01  6:27 ` Peter Wang (王信友)
2024-11-01  7:53 ` Manivannan Sadhasivam
2024-11-01 16:31   ` Bart Van Assche
2024-11-02 10:21     ` Manivannan Sadhasivam
2024-11-01 21:03 ` Bean Huo
2024-11-04 13:43 ` Neil Armstrong
2024-11-05  2:31 ` Martin K. Petersen [this message]
2024-11-05  3:48   ` James Bottomley

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=yq1ttcm4dju.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=lporzio@micron.com \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mikebi@micron.com \
    --cc=neil.armstrong@linaro.org \
    --cc=peter.wang@mediatek.com \
    --cc=quic_mnaresh@quicinc.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