From: Zhang Rui <rui.zhang@intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amit.kucheria@linaro.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Ram Chandrasekar <rkumbako@codeaurora.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/5] thermal: core: Add helpers to browse the cdev, tz and governor list
Date: Wed, 01 Jul 2020 15:57:17 +0800 [thread overview]
Message-ID: <766cbdeb2a0f9d9df4f68a71b4b0defd1e95e0be.camel@intel.com> (raw)
In-Reply-To: <143d954f-2ecf-c4d3-cb7d-f2ea75da8276@linaro.org>
On Wed, 2020-07-01 at 09:35 +0200, Daniel Lezcano wrote:
> On 30/06/2020 17:09, Zhang Rui wrote:
> > Hi, Daniel,
> >
> > seems that you forgot to cc linux-pm mailing list.
> >
> > On Tue, 2020-06-30 at 17:16 +0530, Amit Kucheria wrote:
> > > On Thu, Jun 25, 2020 at 8:15 PM Daniel Lezcano
> > > <daniel.lezcano@linaro.org> wrote:
> > > >
> > > > The cdev, tz and governor list, as well as their respective
> > > > locks
> > > > are
> > > > statically defined in the thermal_core.c file.
> > > >
> > > > In order to give a sane access to these list, like browsing all
> > > > the
> > > > thermal zones or all the cooling devices, let's define a set of
> > > > helpers where we pass a callback as a parameter to be called
> > > > for
> > > > each
> > > > thermal entity.
> > > >
> > > > We keep the self-encapsulation and ensure the locks are
> > > > correctly
> > > > taken when looking at the list.
> > > >
> > > > Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> > > > ---
> > > > drivers/thermal/thermal_core.c | 51
> > > > ++++++++++++++++++++++++++++++++++
> > >
> > > Is the idea to not use thermal_helpers.c from now on? It fits
> > > perfectly with a patch I have to merge all its contents to
> > > thermal_core.c :-)
> >
> > I agree these changes should be in thermal_helper.c
>
> Oh, actually I remind put those functions in the thermal_core.c file
> because they need the locks which are statically defined in there.
>
> If the functions are moved to thermal_helper.c that will imply to
> export
> the locks outside of the file, thus breaking the self-encapsulation.
>
> Do you want to move them out?
Then no. I don't have any objection of removing thermal_helper.c, so
you can just leave these functions in thermal_core.c
thanks,
rui
>
>
next prev parent reply other threads:[~2020-07-01 7:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 14:45 Daniel Lezcano
2020-06-25 14:45 ` [PATCH v2 2/5] thermal: core: Get thermal zone by id Daniel Lezcano
2020-06-30 11:54 ` Amit Kucheria
2020-06-30 15:16 ` Zhang Rui
2020-06-25 14:45 ` [PATCH v2 3/5] thermal: core: Remove old uapi generic netlink Daniel Lezcano
2020-06-30 11:47 ` Amit Kucheria
2020-07-01 9:26 ` Daniel Lezcano
2020-07-01 9:33 ` Amit Kucheria
2020-07-01 9:45 ` Daniel Lezcano
2020-07-01 12:10 ` Amit Kucheria
2020-07-01 12:13 ` Daniel Lezcano
2020-06-25 14:45 ` [PATCH v2 4/5] thermal: core: genetlink support for events/cmd/sampling Daniel Lezcano
2020-06-30 11:45 ` Amit Kucheria
2020-06-30 16:12 ` Zhang Rui
2020-06-30 18:32 ` Daniel Lezcano
2020-07-01 7:41 ` Zhang Rui
2020-07-01 8:22 ` Daniel Lezcano
2020-07-01 15:49 ` Srinivas Pandruvada
2020-07-01 16:31 ` Daniel Lezcano
2020-07-01 16:41 ` Srinivas Pandruvada
2020-06-25 14:45 ` [PATCH v2 5/5] thermal: core: Add notifications call in the framework Daniel Lezcano
2020-06-30 11:49 ` Amit Kucheria
2020-06-30 11:58 ` Daniel Lezcano
2020-06-30 11:46 ` [PATCH v2 1/5] thermal: core: Add helpers to browse the cdev, tz and governor list Amit Kucheria
2020-06-30 15:09 ` Zhang Rui
2020-06-30 18:46 ` Amit Kucheria
2020-07-01 7:08 ` Daniel Lezcano
2020-07-01 7:35 ` Daniel Lezcano
2020-07-01 7:57 ` Zhang Rui [this message]
2020-07-01 9:26 ` Amit Kucheria
2020-07-01 9:54 ` Daniel Lezcano
2020-07-01 9:50 ` Daniel Lezcano
2020-07-02 13:53 ` Zhang Rui
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=766cbdeb2a0f9d9df4f68a71b4b0defd1e95e0be.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=amit.kucheria@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkumbako@codeaurora.org \
--cc=srinivas.pandruvada@linux.intel.com \
/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
Powered by JetHome