From: Jonathan Corbet <corbet@lwn.net>
To: Quentin Perret <quentin.perret@arm.com>
Cc: peterz@infradead.org, rjw@rjwysocki.net, juri.lelli@redhat.com,
mingo@redhat.com, morten.rasmussen@arm.com, qais.yousef@arm.com,
patrick.bellasi@arm.com, dietmar.eggemann@arm.com,
linux-doc@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Documentation: Explain EAS and EM
Date: Wed, 6 Feb 2019 17:32:28 -0700 [thread overview]
Message-ID: <20190206173228.30e99cf4@lwn.net> (raw)
In-Reply-To: <20190121111724.18234-1-quentin.perret@arm.com>
On Mon, 21 Jan 2019 11:17:21 +0000
Quentin Perret <quentin.perret@arm.com> wrote:
> The recently introduced Energy Aware Scheduling (EAS) feature relies on
> a large set of concepts, assumptions, and design choices that are
> probably not obvious for an outsider. Moreover, enabling EAS on a
> particular platform isn't straightforward because of all its
> dependencies. This series tries to address this by introducing proper
> documentation files for the scheduler's part of EAS and for the newly
> introduced Energy Model (EM) framework. These are meant to explain not
> only the design choices of EAS but also to list its dependencies in a
> human-readable location.
So these have been sitting in my folder waiting for acks or some other
sort of discussion, but it's been awfully quiet. Should I take them, or
do they need further work or ... ?
Thanks,
jon
next prev parent reply other threads:[~2019-02-07 0:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 11:17 [PATCH v2 0/3] Documentation: Explain EAS and EM Quentin Perret
2019-01-21 11:17 ` [PATCH v2 1/3] PM / EM: Fix broken kerneldoc Quentin Perret
2019-01-21 11:17 ` [PATCH v2 2/3] PM / EM: Document the Energy Model framework Quentin Perret
2019-01-21 11:17 ` [PATCH v2 3/3] sched: Document Energy Aware Scheduling Quentin Perret
2019-02-07 0:32 ` Jonathan Corbet [this message]
2019-02-07 8:11 ` [PATCH v2 0/3] Documentation: Explain EAS and EM Quentin Perret
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=20190206173228.30e99cf4@lwn.net \
--to=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=quentin.perret@arm.com \
--cc=rjw@rjwysocki.net \
/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).