4 ms·
386 specific workaround code still needed to be updated if relevant part of the code is updated. If you look at the patch the remove 386 support (http://lkml.i
by innocenat 6y ago
386 specific workaround code still needed to be updated if relevant part of the code is updated.
If you look at the patch the remove 386 support (http://lkml.iu.edu/hypermail/linux/kernel/1212.1/01152.html http://lkml.iu.edu/hypermail/linux/kernel/1212.1/01152.html), you can already see that it's already under #ifdef. There are quite a number of atomic instructions not available for 386 which all requires workaround.
- zozbot234 6y agoLooks like that code could have been refactored to be better self-contained. Though I suppose removing it altogether is a fine way to go about it; it can always be reintroduced in the future if folks commit to maintaining the support going forward.