From: Juri Lelli <juri.lelli@redhat.com>
To: Quentin Perret <quentin.perret@arm.com>
Cc: corbet@lwn.net, peterz@infradead.org, rjw@rjwysocki.net,
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 1/2] PM / EM: Document the Energy Model framework
Date: Thu, 17 Jan 2019 15:47:44 +0100 [thread overview]
Message-ID: <20190117144744.GF14385@localhost.localdomain> (raw)
In-Reply-To: <20190110110546.8101-2-quentin.perret@arm.com>
Hi,
On 10/01/19 11:05, Quentin Perret wrote:
> Introduce a documentation file summarizing the key design points and
> APIs of the newly introduced Energy Model framework.
>
> Signed-off-by: Quentin Perret <quentin.perret@arm.com>
Looks good to me.
Reviewed-by: Juri Lelli <juri.lelli@redhat.com>
Best,
- Juri
next prev parent reply other threads:[~2019-01-17 14:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 11:05 [PATCH 0/2] Documentation: Explain EAS and EM Quentin Perret
2019-01-10 11:05 ` [PATCH 1/2] PM / EM: Document the Energy Model framework Quentin Perret
2019-01-17 14:47 ` Juri Lelli [this message]
2019-01-17 14:53 ` Quentin Perret
2019-01-21 11:37 ` [tip:sched/core] PM/EM: " tip-bot for Quentin Perret
2019-01-21 13:53 ` tip-bot for Quentin Perret
2019-01-21 14:10 ` Quentin Perret
2019-01-27 11:36 ` tip-bot for Quentin Perret
2019-01-10 11:05 ` [PATCH 2/2] sched: Document Energy Aware Scheduling Quentin Perret
2019-01-17 15:51 ` Juri Lelli
2019-01-18 9:16 ` Quentin Perret
2019-01-18 9:57 ` Rafael J. Wysocki
2019-01-18 10:34 ` Quentin Perret
2019-01-18 10:58 ` Rafael J. Wysocki
2019-01-18 11:01 ` Rafael J. Wysocki
2019-01-18 11:11 ` Quentin Perret
2019-01-18 11:20 ` Rafael J. Wysocki
2019-01-18 11:26 ` Quentin Perret
2019-01-18 12:34 ` Juri Lelli
2019-01-21 11:38 ` [tip:sched/core] sched/doc: " tip-bot for Quentin Perret
2019-01-21 13:54 ` tip-bot for Quentin Perret
2019-01-27 11:37 ` tip-bot for 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=20190117144744.GF14385@localhost.localdomain \
--to=juri.lelli@redhat.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.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 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.