From: Thorsten Leemhuis on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3884#note_2531922247 FWIW. I could adjust the patch and add a hack to handle mainline with and without !3898 - and once !3898 landed submit another patch to remove the hack. Would this even be a good general strategy for similar cases? I for example could have submitted a patch to handle cpupower.service weeks ago in the kernel.spec.template with some ifdefery to make things work before and after that patch adding that service landed; and than later remove the ifdefery in a follow-up submissions. But to be honest: that would feel like a lot of overhead just to keep the CI happy. -- _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
