[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <43qqvhcxhze7vcip2w3kqulqwzzfinl22kjq5dt7f3gmqe55ac@exknfhnxzy6o>
Date: Sun, 8 Feb 2026 16:46:46 -0500
From: Aaron Tomlin <atomlin@...mlin.com>
To: rafael@...nel.org, dakr@...nel.org, pavel@...nel.org, lenb@...nel.org
Cc: akpm@...ux-foundation.org, bp@...en8.de, pmladek@...e.com,
rdunlap@...radead.org, feng.tang@...ux.alibaba.com, pawan.kumar.gupta@...ux.intel.com,
kees@...nel.org, elver@...gle.com, arnd@...db.de, fvdl@...gle.com,
lirongqing@...du.com, bhelgaas@...gle.com, neelx@...e.com, sean@...e.io,
mproche@...il.com, chjohnst@...il.com, nick.lange@...il.com,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [v2 PATCH 0/1] PM: QoS: Introduce boot parameter
pm_qos_resume_latency_us
On Tue, Jan 27, 2026 at 10:31:42PM -0500, Aaron Tomlin wrote:
> Hi Rafael, Danilo, Pavel, Len,
>
> Users currently lack a mechanism to define granular, per-CPU PM QoS
> resume latency constraints during the early boot phase.
Hi Rafael, Danilo, Pavel, Len,
I am writing to respectfully enquire about the status of this v2 patch
series, initially submitted on the 27th of January.
As it has been approximately two weeks since the submission. Please do let
me know if there are any outstanding concerns or if you require any further
modifications to the series or if you would like me to rebase.
Kind regards,
--
Aaron Tomlin
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists