diff options
author | Quentin Perret <qperret@google.com> | 2022-07-05 14:23:10 +0000 |
---|---|---|
committer | Marc Zyngier <maz@kernel.org> | 2022-07-06 10:00:31 +0100 |
commit | 1c3ace2b8b3995d3213c5e2d2aca01a0577a3b0f (patch) | |
tree | 514746863bf214290d98548fad10d9d5b5f44297 /arch/arm64/kvm/pvtime.c | |
parent | 40c56bd8e1aea7929a09f1d4d68ac3221bb142c4 (diff) |
KVM: arm64: Don't return from void function
Although harmless, the return statement in kvm_unexpected_el2_exception
is rather confusing as the function itself has a void return type. The
C standard is also pretty clear that "A return statement with an
expression shall not appear in a function whose return type is void".
Given that this return statement does not seem to add any actual value,
let's not pointlessly violate the standard.
Build-tested with GCC 10 and CLANG 13 for good measure, the disassembled
code is identical with or without the return statement.
Fixes: e9ee186bb735 ("KVM: arm64: Add kvm_extable for vaxorcism code")
Signed-off-by: Quentin Perret <qperret@google.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20220705142310.3847918-1-qperret@google.com
Diffstat (limited to 'arch/arm64/kvm/pvtime.c')
0 files changed, 0 insertions, 0 deletions