Debian Patches

Status for cpufreqd/2.4.2-3

Patch	Description	Author	Forwarded	Bugs	Origin	Last update
619913.patch	Use power_now instead of current_now to read power from sysfs Apparently, current_now was renamed to power_now around kernel 2.6.36. The fix in this patch first tries to read from the new file name, if this does not exist, it tries the old name. Modification to avoid checking closed battery ===================================================================	Bernd Rinn (z-bb)	no	upstream	https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/733507/+attachment/3022414/+files/cpufreqd-bug%23733507.patch	2012-10-12
ppc64el.patch	<short summary of the patch> TODO: Put a short summary on the line above and replace this paragraph with a longer explanation of this change. Complete the meta-information with other relevant fields (see below for details). To make it easier, the information below has been extracted from the changelog. Adjust it or drop it. . cpufreqd (2.4.2-2) unstable; urgency=low . * Fix reading the correct battery attribute (Closes: #619913 and Closes: #644567).	Mattia Dongili <malattia@debian.org>	no	debian
fix-build-on-power-with-libcpupower-from.patch	Fix build on power* with libcpupower from kernel >= 5.1	Frédéric Bonnard <frediz@debian.org>	no			2019-08-28
fix-build-on-power-since-kernel-5.6.7.patch	Fix build on power since kernel 5.6.7 No need for the wrappers anymore	Frédéric Bonnard <frediz@debian.org>	no			2020-05-05