From: Justin M. Forbes on
gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1408#note_8023...
(2) are we turning this on because there is a Customer need, or
because the
script for configs can't handle it? The former makes sense, but the
latter
would be puzzling to me.
The script for configs can handle any valid configs, the problem is you have
an invalid config. As to what has been reviewed and approved, aarch64 would
have CONFIG_DEVMEM off and CONFIG_STRICT_DEVMEM on. The later would silently
flip CONFIG_DEVMEM to on, but our scripts alert us that it is happening and
will not allow it because it is not what we have set.
If we're going to leave it enabled, we want STRICT_DEVMEM=y so
it's not so
easy to crash the kernel. But turning DEVMEM on only for the -debug
kernel
makes the most sense to me.
I am happy to flip it back to off for aarch64 RHEL configs. The mismatch just
has to be cleared up in one way or another. As it was, we had untracked files
in pending-common.