summaryrefslogtreecommitdiff
path: root/lib/test_hexdump.c
diff options
context:
space:
mode:
authorLukas Bulwahn <lukas.bulwahn@gmail.com>2022-07-07 13:54:42 +0200
committerDave Hansen <dave.hansen@linux.intel.com>2022-07-07 09:51:36 -0700
commit9de76f41ea2188f2784f48352f9278819d249afc (patch)
tree46ae0319bd2d3de02282377a5efaafd8d5023109 /lib/test_hexdump.c
parent018ab4fabddd94f1c96f3b59e180691b9e88d5d8 (diff)
downloadlinux-9de76f41ea2188f2784f48352f9278819d249afc.tar.gz
linux-9de76f41ea2188f2784f48352f9278819d249afc.tar.bz2
linux-9de76f41ea2188f2784f48352f9278819d249afc.zip
x86/mm: Refer to the intended config STRICT_DEVMEM in a comment
Commit a4866aa81251 ("mm: Tighten x86 /dev/mem with zeroing reads") adds a comment to the function devmem_is_allowed() referring to a non-existing config STRICT_IOMEM, whereas the comment very likely intended to refer to the config STRICT_DEVMEM, as the commit adds some behavior for the config STRICT_DEVMEM. Most of the initial analysis was actually done by Dave Hansen in the email thread below (see Link). Refer to the intended and existing config STRICT_DEVMEM. Suggested-by: Dave Hansen <dave.hansen@intel.com> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com> Link: https://lore.kernel.org/r/f9074e8d-9314-9d7d-7bf5-5b5538c8be8d@intel.com/ Link: https://lkml.kernel.org/r/20220707115442.21107-1-lukas.bulwahn@gmail.com
Diffstat (limited to 'lib/test_hexdump.c')
0 files changed, 0 insertions, 0 deletions