This is just guessing and probably triggers the same warning unless
Have the original author look at it.
This is not guesswork.
It is DANGEROUS guesswork. Assigning stuff to itself is pointless, so
this is a code bug.
The only valid exception I know is if you're writing back data to a
command register in a peripheral device, which isn't the case here.
Fix the bug, not the symptom!
I agree, but I can think of another valid exception. System with
Hamming correction on the memory, gets a single bit (correctable)
error. Need to rewrite the memory contents to reset all the parity