From: Jon Hunter <jonathanh@nvidia.com>
To: Jie Zhan <zhanjie9@hisilicon.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Dmitry Osipenko <digetx@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Robie Basak <robibasa@qti.qualcomm.com>
Subject: Re: [PATCH] devreq: move governor.h to a public header location
Date: Fri, 26 Sep 2025 11:33:13 +0100 [thread overview]
Message-ID: <25692922-7610-49bc-b33d-c799a13995cb@nvidia.com> (raw)
In-Reply-To: <ae509446-4703-43af-a48d-9c72da0b3813@hisilicon.com>
On 26/09/2025 04:16, Jie Zhan wrote:
>
> Hi Dmitry,
>
> On 9/3/2025 9:43 PM, Dmitry Baryshkov wrote:
>> Some device drivers (and out-of-tree modules) might want to define
>> device-specific device governors. Rather than restricting all of them to
>> be a part of drivers/devfreq/ (which is not possible for out-of-tree
>> drivers anyway) move governor.h to include/linux/devfreq-governor.h and
>> update all drivers to use it.
>
> For out-of-tree module compilation, can it add drivers/devfreq/ to the
> include path?
> I suppose this is unnecessary.
The kernel header/source package created for most linux distros will not
included this header because it is internal and so in that case it is
necessary.
Jon
--
nvpublic
next prev parent reply other threads:[~2025-09-26 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 13:43 [PATCH] devreq: move governor.h to a public header location Dmitry Baryshkov
2025-09-16 17:24 ` Dmitry Baryshkov
2025-09-17 13:39 ` Jon Hunter
2025-09-18 1:57 ` Mikko Perttunen
2025-09-26 3:16 ` Jie Zhan
2025-09-26 10:33 ` Jon Hunter [this message]
2025-09-28 2:01 ` Jie Zhan
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=25692922-7610-49bc-b33d-c799a13995cb@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=cw00.choi@samsung.com \
--cc=digetx@gmail.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=robibasa@qti.qualcomm.com \
--cc=thierry.reding@gmail.com \
--cc=zhanjie9@hisilicon.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