On 02/11/2022 07:27, Jan Beulich wrote:
On 02.11.2022 04:00, Henry Wang wrote: >>
Also I think we need to submit a patch to make the default CONFIG_DEBUG
to n in Kconfig? Thanks!
Iirc what was done in 4.16 was to switch to non-debug immediately after
branching, on the new branch only. That was specifically to keep debug
enabled at all times (and no undue code churn) in staging. Debug
intermediately off was (earlier on) observed to result in huge Coverity
reports, because of the perceived differences in the pre-processed /
produced code.
That's correct. I will send the patch once we agreed when to branch.
@Henry, From the previous discussion, it seems like we still have some
blocker. Do we have any update on them?
Cheers,
--
Julien Grall
