x86/vm86: Make sure the free_vm86(task) definition uses its parameter even in the !CONFIG_VM86 case

I ran into a case in new code where free_vm86(task) was the only
consumer of the 'task' variable:

  arch/x86/kernel/process.c: In function ‘exit_thread’:
  arch/x86/kernel/process.c:118:31: error: unused variable ‘t’ [-Werror=unused-variable]

Robustify the definition in the !CONFIG_VM86 case.

Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://lore.kernel.org/r/ZgaFfyHMOdLHEKm+@gmail.com
This commit is contained in:
Ingo Molnar
2024-03-29 14:20:40 +01:00
parent 5d31174f3c
commit 5ca28d24ae

View File

@ -84,7 +84,7 @@ static inline int handle_vm86_trap(struct kernel_vm86_regs *a, long b, int c)
static inline void save_v86_state(struct kernel_vm86_regs *a, int b) { } static inline void save_v86_state(struct kernel_vm86_regs *a, int b) { }
#define free_vm86(t) do { } while(0) #define free_vm86(task) do { (void)(task); } while(0)
#endif /* CONFIG_VM86 */ #endif /* CONFIG_VM86 */