Everything here applies to this as well. Thanks, VMware. In Microsoft's case it turned out that nothing was using that value and it could be replaced without breaking things. With luck that's true here as well.
Catching these kinds of intentionally offensive hex values at submission time rather than later on, and programmatically searching them out in existing code.
It just occurred to me that the terms "hexism" and "hexist" apply nicely to this.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Re: checkpatch?
(Anonymous) 2012-11-14 12:25 am (UTC)(link)It just occurred to me that the terms "hexism" and "hexist" apply nicely to this.
Re: checkpatch?
(Anonymous) 2012-11-14 09:11 am (UTC)(link)People become way too sensitive this days.