Just to be clear, these are both upstream commits. Is there any work going on upstream to resolve the issue?
Currently eoan is using a kernel copied forward from disco, but we should be putting a 5.2 kernel into eoan-proposed within the next couple of weeks. This is likely to be before we could expect to see them in a disco-proposed kernel, as the patch deadline for the next kernel SRU cycle has passed.
I agree that the likelihood of regressions is slim for us, as the changes were made only to support builds using clang. So I will go ahead and revert these in our 5.2 tree.
I'm not sure why there's a xenial nomination here for a ftbfs in eoan though ...
Just to be clear, these are both upstream commits. Is there any work going on upstream to resolve the issue?
Currently eoan is using a kernel copied forward from disco, but we should be putting a 5.2 kernel into eoan-proposed within the next couple of weeks. This is likely to be before we could expect to see them in a disco-proposed kernel, as the patch deadline for the next kernel SRU cycle has passed.
I agree that the likelihood of regressions is slim for us, as the changes were made only to support builds using clang. So I will go ahead and revert these in our 5.2 tree.
I'm not sure why there's a xenial nomination here for a ftbfs in eoan though ...