Hi Francesco,

On Tue, Mar 18, 2025 at 06:27:52PM +0100, Francesco Poli wrote:
> On Mon, 17 Mar 2025 21:21:53 +0100 Salvatore Bonaccorso wrote:
> 
> [...]
> > On Mon, Mar 10, 2025 at 07:25:37PM +0100, Francesco Poli wrote:
> [...]
> > > Is there any chance to see the three files included in the
> > > 'linux-cpupower' package?
> [...]
> > Let me try to quickly summarize the status here (don't shoot the
> > messenger):
> > 
> > From a src:linux maintenance point of view I think we would still
> > continue to decline shipping some scripts in packages produced, but
> > there might be a chance we ship them if they are maintained upstream
> > as examples (FWIW, this is very similar argument as it holds for which
> > patches we accept to cherry-pick, only what is reviewed and accepted
> > upstream and is applied in at least a upper version)
> > 
> > My proposal to you would be: Do upstream the scripts as part of the
> > tools/power/cpupower source. If they get accepted we might include them
> > as part of upstream as well in the produced packages.
> 
> Hello Salvatore,
> thanks for your followup.
> 
> I can try, hoping that the answer won't be "this is a job for distros,
> not for upstream!"...
>
> Where do I start from?
> By sending a message to the [linux-pm] mailing list?
> 
> [linux-pm]: <https://lore.kernel.org/linux-pm/>
> 
> Please let me know, thanks for your time.

That is where I would start as well. Or more specific looking what
"get_maintainer.pl" gives me:

$ ./scripts/get_maintainer.pl ./tools/power/cpupower/
Thomas Renninger <[email protected]> (maintainer:CPU POWER MONITORING SUBSYSTEM)
Shuah Khan <[email protected]> (maintainer:CPU POWER MONITORING SUBSYSTEM)
"John B. Wyatt IV" <[email protected]> (maintainer:CPU POWER MONITORING 
SUBSYSTEM)
John Kacur <[email protected]> (maintainer:CPU POWER MONITORING SUBSYSTEM)
[email protected] (open list:CPU POWER MONITORING SUBSYSTEM)
[email protected] (open list)

That means apart from using the linux-pm  mailinglist, add as well as
recipients the respecive maintainers responsible.

Hope that helps you to start, feel free to as well CC the Debian bug
so that (or at least point out when you have started the discussion
upstream so that we can mark the bug forwarded).

Regards,
Salvatore

Reply via email to