[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aMnB36jJ14o68mGF@google.com>
Date: Tue, 16 Sep 2025 13:00:31 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Paolo Bonzini <pbonzini@...hat.com>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Liao Yuanhong <liaoyuanhong@...o.com>
Subject: Re: [PATCH] x86/apic: KVM: Use guard() instead of mutex_lock() to
simplify code
On Mon, Sep 15, 2025, Sean Christopherson wrote:
> On Mon, 01 Sep 2025 21:18:21 +0800, Liao Yuanhong wrote:
> > Using guard(mutex) instead of mutex_lock/mutex_unlock pair. Simplifies the
> > error handling to just return in case of error. No need for the 'out' label
> > and variable 'ret' anymore so remove it.
>
> Applied to kvm-x86 misc, thanks!
>
> [1/1] x86/apic: KVM: Use guard() instead of mutex_lock() to simplify code
> https://github.com/kvm-x86/linux/commit/50f4db196766
I force pushed to fixup an unrelated commit, new hash:
https://github.com/kvm-x86/linux/commit/4319fa120f0f
Powered by blists - more mailing lists