summaryrefslogtreecommitdiff
path: root/drivers/bus/bt1-apb.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2023-06-28 12:47:30 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2023-06-28 12:47:30 -0700
commit1b2c92a1cb2469d8c0079dbf496ab86e22e1cb7c (patch)
tree19270949f54df0c061e246258712132a72ef7ead /drivers/bus/bt1-apb.c
parent6581ccf03e717926be97dc3d27182ce351232f3c (diff)
x86/mem_encrypt: Remove stale mem_encrypt_init() declaration
The memory encryption initialization logic was moved from init/main.c into arch_cpu_finalize_init() in commit 439e17576eb4 ("init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init()"), but a stale declaration for the init function was left in <linux/init.h>. And didn't cause any problems if you had X86_MEM_ENCRYPT enabled, which apparently everybody involved did have. See also commit 0a9567ac5e6a ("x86/mem_encrypt: Unbreak the AMD_MEM_ENCRYPT=n build") in this whole sad saga of conflicting declarations for different situations. Reported-by: Matthew Wilcox <willy@infradead.org> Fixes: 439e17576eb4 init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init() Cc: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/bus/bt1-apb.c')
0 files changed, 0 insertions, 0 deletions