summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorSergey Senozhatsky <senozhatsky@chromium.org>2025-12-15 08:47:12 +0300
committerAndrew Morton <akpm@linux-foundation.org>2026-01-21 06:24:38 +0300
commitbde60fe747216d3449a1a74f07937a5273717b69 (patch)
treeee2d5df60ecf969e6ef16e96d01bf497e1c89db1 /include/linux
parent2e8ff2f51dde73a26b94aed2df4827177bd25e6e (diff)
downloadlinux-bde60fe747216d3449a1a74f07937a5273717b69.tar.xz
zram: rename internal slot API
We have a somewhat confusing internal API naming. E.g. the following code: zram_slot_lock() if (zram_allocated()) zram_set_flag() zram_slot_unlock() may look like it does something on zram device level, but in fact it tests and sets slot entry flags, not the device ones. Rename API to explicitly distinguish functions that operate on the slot level from functions that operate on the zram device level. While at it, fixup some coding styles. [senozhatsky@chromium.org: fix up mark_slot_accessed()] Link: https://lkml.kernel.org/r/20260115031922.3813659-1-senozhatsky@chromium.org Link: https://lkml.kernel.org/r/775a0b1a0ace5caf1f05965d8bc637c1192820fa.1765775954.git.senozhatsky@chromium.org Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org> Cc: Brian Geffon <bgeffon@google.com> Cc: David Stevens <stevensd@google.com> Cc: Minchan Kim <minchan@google.com> Cc: Richard Chang <richardycc@google.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions