-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/18/2010 09:28 AM, Michal Marek wrote:
On 18.8.2010 15:19, Greg KH wrote:
On Wed, Aug 18, 2010 at 02:23:04PM +0200, Michal Marek wrote:
The drivers_pci change was my fault, but after importing the symset files as well, there is still
$ rpm -ivh --test ati-fglrxG02-kmp-default-8.741_k2.6.34.0_12-28.1.x86_64.rpm nvidia-gfxG02-kmp-default-256.35_k2.6.34.0_12-14.1.x86_64.rpm nvidia-gfxG01-kmp-default-173.14.27_k2.6.34.0_12-22.1.x86_64.rpm 2>&1 | grep 'kernel(' kernel(default:arch_x86_kernel_acpi) = 59664e86a426f5a6 is needed by ati-fglrxG02-kmp-default-8.741_k2.6.34.0_12-28.1.x86_64
The arch_x86_kernel_acpi symset changed because of changes in struct acpi_power_register and struct acpi_processor_cx introduced by commit 718be4a (ACPI: skip checking BM_STS if the BIOS doesn't ask for it). As these structures seem to be used only internally by the acpi implementation, so I'd vote for hiding it with the __GENKSYMS__ hack and removing the two functions from the whitelist.
Using __GENKSYMS__ is fine, want me to do it?
But what do you mean by "remove two functions from the whitelist"?
Jeff added acpi_processor_ffh_cstate_* PASS drivers/acpi/processor PASS to kabi/severities, which makes the kabi checker ignore the change.
Ok, I have a patch for this now. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkxuwKQACgkQLPWxlyuTD7JlHACfRaUVql5yNR5PJHf38CbqQ8UW 2H0AnAi341pPU7dVu7+gNd6CXcMdqseQ =YqrK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org