From: Matthias Kaehlcke <mka@chromium.org>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: andrew-sh.cheng@mediatek.com, hsinyi@chromium.org,
sibis@codeaurora.org, saravanak@google.com,
myungjoo.ham@samsung.com, kyungmin.park@samsung.com,
chanwoo@kernel.org, cwchoi00@gmail.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] PM / devfreq: Export devfreq_get_freq_ragne symbol within devfreq
Date: Tue, 22 Jun 2021 11:23:44 -0700 [thread overview]
Message-ID: <YNIqsJLqWNSg2oxM@google.com> (raw)
In-Reply-To: <20210617060546.26933-3-cw00.choi@samsung.com>
On Thu, Jun 17, 2021 at 03:05:44PM +0900, Chanwoo Choi wrote:
> Subject: PM / devfreq: Export devfreq_get_freq_ragne symbol within devfreq
nit: s/ragne/range/
>
> In order to get frequency range within devfreq governors,
> export devfreq_get_freq_ragne symbol within devfreq.
>
> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
next prev parent reply other threads:[~2021-06-22 18:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210617054647epcas1p3f1ef3ddef736496151ff77df4f50749a@epcas1p3.samsung.com>
2021-06-17 6:05 ` [PATCH 0/4] PM / devfreq: Add cpu based scaling support to passive governor Chanwoo Choi
2021-06-17 6:05 ` [PATCH 1/4] PM / devfreq: passive: Fix get_target_freq when not using required-opp Chanwoo Choi
2021-06-24 1:38 ` Chanwoo Choi
2021-06-17 6:05 ` [PATCH 2/4] PM / devfreq: Export devfreq_get_freq_ragne symbol within devfreq Chanwoo Choi
2021-06-22 18:23 ` Matthias Kaehlcke [this message]
2021-07-13 19:36 ` Chanwoo Choi
2021-06-17 6:05 ` [PATCH 3/4] PM / devfreq: Add cpu based scaling support to passive governor Chanwoo Choi
2021-06-17 5:51 ` Hsin-Yi Wang
2021-06-17 6:13 ` Chanwoo Choi
2021-06-22 17:42 ` Matthias Kaehlcke
2021-06-22 18:36 ` Matthias Kaehlcke
2021-06-17 6:05 ` [PATCH 4/4] PM / devfreq: passive: Reduce duplicate code when passive_devfreq case Chanwoo Choi
2021-06-22 18:35 ` Matthias Kaehlcke
2021-07-13 19:31 ` Chanwoo Choi
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=YNIqsJLqWNSg2oxM@google.com \
--to=mka@chromium.org \
--cc=andrew-sh.cheng@mediatek.com \
--cc=chanwoo@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=cwchoi00@gmail.com \
--cc=hsinyi@chromium.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=saravanak@google.com \
--cc=sibis@codeaurora.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