if just that patch doesn't make it, well, ok for me. I just
think
CONFIG_STRICT_DEVMEM is superfluous when the runtime configuration
option is present.
It should always be "N" because the only other option means "add
pointless code of no value whatsoever"
Which means strict_devmem really belongs in the bitbucket as a bad idea
Alan