From: Faruque Ansari <faruque.ansari@oss.qualcomm.com>
To: Sebastian Reichel <sre@kernel.org>,
Benson Leung <bleung@chromium.org>,
Tzung-Bi Shih <tzungbi@kernel.org>,
Guenter Roeck <groeck@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Matti Vaittinen <mazziesaccount@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, chrome-platform@lists.linux.dev,
avaneesh.dwivedi@oss.qualcomm.com,
Umang Chheda <umang.chheda@oss.qualcomm.com>,
Ulf Hansson <ulfh@kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>,
Bradley Morgan <brads@mainlining.org>,
kernel test robot <lkp@intel.com>,
Francesco Valla <francesco@valla.it>
Subject: Re: [PATCH v17 0/6] power: reset: Introduce the Power State Change Reasons Recording (PSCRR) framework
Date: Mon, 2 Nov 2026 12:53:52 +0530 [thread overview]
Message-ID: <310fd443-4cbc-4dcc-884f-6cd23d5f9c10@oss.qualcomm.com> (raw)
In-Reply-To: <20261019-pscrr-framework-v17-0-69ea6cdf4731@oss.qualcomm.com>
Hi Sebastian,
Gentle ping on this series. I've addressed all the comments
raised till v16, and there are no outstanding concerns on v17
from any maintainer --Matti, Daniel, and Bradley have reviewed
with Reviewed-by tags, and you already gave one on patch 1.
Please let me know your thoughts, or if there's anything you'd
like me to revise.
Thanks,
Faruque Ansari
prev parent reply other threads:[~2026-11-02 7:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 7:38 Faruque Ansari
2026-10-19 7:38 ` [PATCH v17 1/6] power: Extend power_on_reason.h for upcoming PSCRR framework Faruque Ansari
2026-10-19 7:38 ` [PATCH v17 2/6] reboot: hw_protection_trigger: use standardized numeric shutdown/reboot reasons instead of strings Faruque Ansari
2026-10-19 7:38 ` [PATCH v17 3/6] reboot: add parsable tokens for power state change reasons Faruque Ansari
2026-10-19 7:38 ` [PATCH v17 4/6] reboot: extend psc_reason with power-on and reset causes Faruque Ansari
2026-10-19 7:58 ` Daniel Lezcano
2026-10-19 7:38 ` [PATCH v17 5/6] power: reset: Introduce PSCR Recording Framework for Non-Volatile Storage Faruque Ansari
2026-10-19 7:38 ` [PATCH v17 6/6] Documentation: Add sysfs documentation for PSCRR Faruque Ansari
2026-11-02 7:23 ` Faruque Ansari [this message]
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=310fd443-4cbc-4dcc-884f-6cd23d5f9c10@oss.qualcomm.com \
--to=faruque.ansari@oss.qualcomm.com \
--cc=avaneesh.dwivedi@oss.qualcomm.com \
--cc=bleung@chromium.org \
--cc=brads@mainlining.org \
--cc=broonie@kernel.org \
--cc=chrome-platform@lists.linux.dev \
--cc=daniel.lezcano@kernel.org \
--cc=daniel.lezcano@oss.qualcomm.com \
--cc=francesco@valla.it \
--cc=groeck@chromium.org \
--cc=kernel@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lukasz.luba@arm.com \
--cc=mazziesaccount@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sebastian.reichel@collabora.com \
--cc=sre@kernel.org \
--cc=tzungbi@kernel.org \
--cc=ulfh@kernel.org \
--cc=umang.chheda@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®