Shortly after enabling PWRU support in T8496 we've noticed a spike in the Kernel Source TAR ball which is auto generated after each Kernel build.

This spiked from less then 1GB to 4GB as the vmlinuz.o increased from 54M to 618M just as one candidate due ti enabling of the additional debug symbols.

There is no need in shipping all intermediate objects generated during the Kernel build in our tar file - which holds the source of the Kernel an custom patches. Kernel can be re-compiled if objects are needed.

We will change the behavior to run make mrproper before calling tar on the Kernel source tree.