Yes, this is a big uber-patch. But with the git-am apply method, it still
splits them out in the prepped tree. There's really no advantage to listing
78 patches in the spec at this point as kdbus is likely to go all-or-nothing
if/when it is merged.
- Add Crystal Cove PMIC support necessary to access the PMIC
on many BayTrail tablets
- Add support for Intel PMIC operation regions, as added in
b1eea857d8c70dc3789cc2231e3c0a273a67ba06 upstream and necessary
for battery/charge operations on BayTrail systems
- Add AXP288 ADC and fuel gauge support, as used in many BayTrail SoCs
So. Because of the joys of how perf builds up its LDFLAGS, builds started
failing in rawhide with the latest perl build. See, perf thinks it is a
good idea to look at perl (and python too) and see what ld options were
used to build it, then just slam those into what it uses. That's cute, and
probably kind of works, but with the hardening changes it totally broke
the build. One of the final links failed with:
/usr/bin/ld: perf-in.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
perf-in.o: error adding symbols: Bad value
because it sucked in the hardened build LD options from perl, but didn't
we didn't pass in the required CFLAGS options. Isn't that special?
Fix this by specifying both LDFLAGS (so it isn't magically getting applied
without thought) and EXTRA_CFLAGS for the perf build.
I hate everything.
We very very rarely use these. The last time compile-fixes.patch was
used was over 3 years ago. The upstream-reverts.patch has literally
never been used since Fedora switched to git. We tend to apply the
reverts as stand-alone patches anyway, and compile fixes are generally
better as stand-alone patches that get sent upstream ASAP.
