From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Oleg Nesterov <oleg@redhat.com>, Ingo Molnar <mingo@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mel Gorman <mgorman@suse.de>, Will Deacon <will@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@kernel.org>, Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] Freezer rewrite
Date: Wed, 30 Jun 2021 19:05:36 +0200 [thread overview]
Message-ID: <CAJZ5v0j8MYBq1+dM-VaH6eA28bTMWV-U7Vk6K2Obf2A8mO17-g@mail.gmail.com> (raw)
In-Reply-To: <20210624092156.332208049@infradead.org>
On Thu, Jun 24, 2021 at 11:28 AM Peter Zijlstra <peterz@infradead.org> wrote:
>
> Hi all,
>
> Now with a completely different approach to freezing the special states.
>
> Patches go on top of tip/master, as they depend on the
> task_struct::state rename.
Acked-by: Rafael J. Wysocki <rafael@kernel.org>
for the entire series from the power management side.
next prev parent reply other threads:[~2021-06-30 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 9:21 [PATCH v2 0/4] Freezer rewrite Peter Zijlstra
2021-06-24 9:21 ` [PATCH v2 1/4] freezer: Have {,un}lock_system_sleep() save/restore flags Peter Zijlstra
2021-06-24 9:21 ` [PATCH v2 2/4] freezer,umh: Clean up freezer/initrd interaction Peter Zijlstra
2021-06-24 9:21 ` [PATCH v2 3/4] ptrace: Track __TASK_TRACED state in p->ptrace Peter Zijlstra
2021-06-24 9:22 ` [PATCH v2 4/4] freezer,sched: Rewrite core freezer logic Peter Zijlstra
2021-07-07 14:14 ` Oleg Nesterov
2021-08-05 11:50 ` Peter Zijlstra
2021-06-30 17:05 ` Rafael J. Wysocki [this message]
2021-07-06 13:12 ` [PATCH v2 0/4] Freezer rewrite Peter Zijlstra
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=CAJZ5v0j8MYBq1+dM-VaH6eA28bTMWV-U7Vk6K2Obf2A8mO17-g@mail.gmail.com \
--to=rafael@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).