From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
Bean Huo <huobean@gmail.com>, Avri Altman <avri.altman@wdc.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Can Guo <cang@codeaurora.org>,
Asutosh Das <asutoshd@codeaurora.org>,
Bart Van Assche <bvanassche@acm.org>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH V4 0/2] scsi: ufs: Fix runtime PM messages never-ending cycle
Date: Tue, 01 Mar 2022 23:54:36 -0500 [thread overview]
Message-ID: <yq1h78hymxb.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20220228113652.970857-1-adrian.hunter@intel.com> (Adrian Hunter's message of "Mon, 28 Feb 2022 13:36:50 +0200")
Adrian,
> Kernel messages produced during runtime PM can cause a never-ending
> cycle because user space utilities (e.g. journald or rsyslog) write
> the messages back to storage, causing runtime resume, more messages,
> and so on.
>
> Messages that tell of things that are expected to happen, are arguably
> unnecessary, so make changes to suppress them for the UFS driver.
Applied to 5.18/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-03-02 4:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 11:36 [PATCH V4 0/2] scsi: ufs: Fix runtime PM messages never-ending cycle Adrian Hunter
2022-02-28 11:36 ` [PATCH V4 1/2] scsi: Add quiet_suspend flag for SCSI devices to suppress some PM messages Adrian Hunter
2022-02-28 11:36 ` [PATCH V4 2/2] scsi: ufs: Fix runtime PM messages never-ending cycle Adrian Hunter
2022-03-02 4:54 ` Martin K. Petersen [this message]
2022-03-09 4:15 ` [PATCH V4 0/2] " 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=yq1h78hymxb.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=huobean@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.