Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Marc Zyngier <maz@kernel.org>
To:     kvmarm@lists.cs.columbia.edu, Will Deacon <will@kernel.org>,
        Alexandru Elisei <alexandru.elisei@arm.com>,
        Oliver Upton <oliver.upton@linux.dev>,
        linux-arm-kernel@lists.infradead.org,
        Catalin Marinas <catalin.marinas@arm.com>,
        linux-kernel@vger.kernel.org, Quentin Perret <qperret@google.com>,
        James Morse <james.morse@arm.com>,
        Suzuki K Poulose <suzuki.poulose@arm.com>
Cc:     kernel-team@android.com
Subject: Re: [PATCH] KVM: arm64: Don't return from void function
Date:   Wed,  6 Jul 2022 10:00:58 +0100
Message-Id: <165709805020.885966.4815879973915586287.b4-ty@kernel.org>
In-Reply-To: <20220705142310.3847918-1-qperret@google.com>
References: <20220705142310.3847918-1-qperret@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 5 Jul 2022 14:23:10 +0000, Quentin Perret wrote:
> 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.
> 
> [...]

Applied to kvm-arm64/misc-5.20, thanks!

[1/1] KVM: arm64: Don't return from void function
      commit: 1c3ace2b8b3995d3213c5e2d2aca01a0577a3b0f

Cheers,

	M.
-- 
Marc Zyngier <maz@kernel.org>