From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thara Gopinath <thara.gopinath@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Zhang, Rui" <rui.zhang@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Amit Kachhap <amit.kachhap@gmail.com>,
Javi Merino <javi.merino@kernel.org>,
Eduardo Valentin <edubezval@gmail.com>,
Linux PM <linux-pm@vger.kernel.org>,
Quentin Perret <quentin.perret@arm.com>,
ionela.voinescu@arm.com,
Vincent Guittot <vincent.guittot@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
Juri Lelli <juri.lelli@redhat.com>,
Patrick Bellasi <patrick.bellasi@arm.com>
Subject: Re: [PATCH 1/2] sched/cpufreq: Reorganize the cpufreq files
Date: Thu, 18 Oct 2018 12:06:18 +0200 [thread overview]
Message-ID: <CAJZ5v0ia6jc80=xTkOSZofhmx80UXn2Kv-mPJ6B4JZ-Sc75kBA@mail.gmail.com> (raw)
In-Reply-To: <8585bac0-c72c-edf4-2e93-c8740a3b1b6c@linaro.org>
On Thu, Oct 18, 2018 at 11:54 AM Daniel Lezcano
<daniel.lezcano@linaro.org> wrote:
>
> On 18/10/2018 11:42, Rafael J. Wysocki wrote:
> > On Thu, Oct 18, 2018 at 11:36 AM Daniel Lezcano
> > <daniel.lezcano@linaro.org> wrote:
> >>
> >> It was suggested to set the scene for the PM components in the
> >> scheduler code organization in the recent discussion about making the
> >> scheduler aware of the capacity capping from the thermal framework.
> >>
> >> Move the cpufreq files into its own directory as suggested at:
> >>
> >> https://lkml.org/lkml/2018/10/18/353
> >> https://lkml.org/lkml/2018/10/18/408
> >
> > Fair enough, but do we need to do that right now?
>
> I'm not planning to do more code reorg than this patch right now. Up to
> you to decide if you are willing to take them.
The SPDX one certainly is applicable, but I'm not sure about the other one TBH.
Why don't you add the SPDX IDs to those files as they are for now?
WARNING: multiple messages have this Message-ID (diff)
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thara Gopinath <thara.gopinath@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Zhang, Rui" <rui.zhang@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Amit Kachhap <amit.kachhap@gmail.com>,
Javi Merino <javi.merino@kernel.org>,
Eduardo Valentin <edubezval@gmail.com>,
Linux PM <linux-pm@vger.kernel.org>,
Quentin Perret <quentin.perret@arm.com>,
ionela.voinescu@arm.com,
Vincent Guittot <vincent.guittot@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
Juri Lelli <juri.lelli@redhat.com>,
Patrick Bellasi <patrick.bellasi@a>
Subject: Re: [PATCH 1/2] sched/cpufreq: Reorganize the cpufreq files
Date: Thu, 18 Oct 2018 12:06:18 +0200 [thread overview]
Message-ID: <CAJZ5v0ia6jc80=xTkOSZofhmx80UXn2Kv-mPJ6B4JZ-Sc75kBA@mail.gmail.com> (raw)
In-Reply-To: <8585bac0-c72c-edf4-2e93-c8740a3b1b6c@linaro.org>
On Thu, Oct 18, 2018 at 11:54 AM Daniel Lezcano
<daniel.lezcano@linaro.org> wrote:
>
> On 18/10/2018 11:42, Rafael J. Wysocki wrote:
> > On Thu, Oct 18, 2018 at 11:36 AM Daniel Lezcano
> > <daniel.lezcano@linaro.org> wrote:
> >>
> >> It was suggested to set the scene for the PM components in the
> >> scheduler code organization in the recent discussion about making the
> >> scheduler aware of the capacity capping from the thermal framework.
> >>
> >> Move the cpufreq files into its own directory as suggested at:
> >>
> >> https://lkml.org/lkml/2018/10/18/353
> >> https://lkml.org/lkml/2018/10/18/408
> >
> > Fair enough, but do we need to do that right now?
>
> I'm not planning to do more code reorg than this patch right now. Up to
> you to decide if you are willing to take them.
The SPDX one certainly is applicable, but I'm not sure about the other one TBH.
Why don't you add the SPDX IDs to those files as they are for now?
next prev parent reply other threads:[~2018-10-18 10:06 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181009162509epcas1p4fdd2e23039caa24586a4a52c6d2e7336@epcas1p4.samsung.com>
2018-10-09 16:24 ` [RFC PATCH 0/7] Introduce thermal pressure Thara Gopinath
2018-10-09 16:24 ` [RFC PATCH 1/7] sched/pelt.c: Add option to make load and util calculations frequency invariant Thara Gopinath
2018-10-09 16:24 ` [RFC PATCH 2/7] sched/pelt.c: Add support to track thermal pressure Thara Gopinath
2018-10-09 16:24 ` [RFC PATCH 3/7] sched: Add infrastructure to store and update instantaneous " Thara Gopinath
2018-10-09 16:24 ` [RFC PATCH 4/7] sched: Initialize per cpu thermal pressure structure Thara Gopinath
2018-10-09 16:25 ` [RFC PATCH 5/7] sched/fair: Enable CFS periodic tick to update thermal pressure Thara Gopinath
2018-12-04 15:43 ` Vincent Guittot
2018-10-09 16:25 ` [RFC PATCH 6/7] sched/fair: update cpu_capcity to reflect " Thara Gopinath
2018-10-10 5:57 ` Javi Merino
2018-10-10 14:22 ` Thara Gopinath
2018-10-09 16:25 ` [RFC PATCH 7/7] thermal/cpu-cooling: Update thermal pressure in case of a maximum frequency capping Thara Gopinath
2018-10-10 5:44 ` [RFC PATCH 0/7] Introduce thermal pressure Javi Merino
2018-10-10 14:15 ` Thara Gopinath
2018-10-10 6:17 ` Ingo Molnar
2018-10-10 8:29 ` Quentin Perret
2018-10-10 8:50 ` Vincent Guittot
2018-10-10 9:55 ` Quentin Perret
2018-10-10 10:14 ` Vincent Guittot
2018-10-10 10:36 ` Quentin Perret
2018-10-10 12:04 ` Vincent Guittot
2018-10-10 12:23 ` Juri Lelli
2018-10-10 12:34 ` Vincent Guittot
2018-10-10 12:50 ` Juri Lelli
2018-10-10 13:08 ` Vincent Guittot
2018-10-10 13:34 ` Juri Lelli
2018-10-10 13:38 ` Vincent Guittot
2018-10-10 17:08 ` Thara Gopinath
2018-10-10 13:11 ` Quentin Perret
2018-10-10 13:05 ` Quentin Perret
2018-10-10 13:27 ` Vincent Guittot
2018-10-10 13:47 ` Quentin Perret
2018-10-10 15:19 ` Vincent Guittot
2018-10-10 16:15 ` Ionela Voinescu
2018-10-10 17:03 ` Thara Gopinath
2018-10-10 15:43 ` Thara Gopinath
2018-10-16 7:33 ` Ingo Molnar
2018-10-16 9:28 ` Lukasz Luba
2018-10-17 16:21 ` Thara Gopinath
2018-10-18 6:48 ` Ingo Molnar
2018-10-18 7:08 ` Rafael J. Wysocki
2018-10-18 7:50 ` Ingo Molnar
2018-10-18 8:14 ` Rafael J. Wysocki
2018-10-18 9:35 ` [PATCH 1/2] sched/cpufreq: Reorganize the cpufreq files Daniel Lezcano
2018-10-18 9:35 ` [PATCH 2/2] sched/cpufreq: Add the SPDX tags Daniel Lezcano
2018-10-18 9:42 ` [PATCH 1/2] sched/cpufreq: Reorganize the cpufreq files Rafael J. Wysocki
2018-10-18 9:42 ` Rafael J. Wysocki
2018-10-18 9:54 ` Daniel Lezcano
2018-10-18 10:06 ` Rafael J. Wysocki [this message]
2018-10-18 10:06 ` Rafael J. Wysocki
2018-10-18 10:13 ` Daniel Lezcano
2018-10-18 9:45 ` Daniel Lezcano
2018-10-19 5:24 ` kbuild test robot
2018-10-19 5:52 ` kbuild test robot
2018-10-18 9:44 ` [PATCH V2 " Daniel Lezcano
2018-10-18 9:44 ` [PATCH V2 2/2] sched/cpufreq: Add the SPDX tags Daniel Lezcano
2018-10-18 16:17 ` [RFC PATCH 0/7] Introduce thermal pressure Thara Gopinath
2018-10-19 8:02 ` Ingo Molnar
2018-10-19 11:29 ` Valentin Schneider
2018-10-10 15:35 ` Lukasz Luba
2018-10-10 16:54 ` Daniel Lezcano
2018-10-11 7:35 ` Lukasz Luba
2018-10-11 8:23 ` Daniel Lezcano
2018-10-12 9:37 ` Lukasz Luba
2018-10-10 17:30 ` Thara Gopinath
2018-10-11 11:10 ` Lukasz Luba
2018-10-16 17:11 ` Vincent Guittot
2018-10-17 16:24 ` Thara Gopinath
2018-10-18 8:00 ` Lukasz Luba
2018-10-18 8:12 ` Lukasz Luba
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='CAJZ5v0ia6jc80=xTkOSZofhmx80UXn2Kv-mPJ6B4JZ-Sc75kBA@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=amit.kachhap@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ionela.voinescu@arm.com \
--cc=javi.merino@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=quentin.perret@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rui.zhang@intel.com \
--cc=thara.gopinath@linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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 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.