[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <175798207153.624508.1085968130364515751.b4-ty@google.com>
Date: Mon, 15 Sep 2025 17:25:39 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, Vitaly Kuznetsov <vkuznets@...hat.com>,
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] KVM: x86: hyper-v: Use guard() instead of mutex_lock() to
simplify code
On Mon, 01 Sep 2025 21:16:04 +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_unlock' label anymore so remove it.
Applied to kvm-x86 misc, thanks!
[1/1] KVM: x86: hyper-v: Use guard() instead of mutex_lock() to simplify code
https://github.com/kvm-x86/linux/commit/864384e97981
--
https://github.com/kvm-x86/linux/tree/next
Powered by blists - more mailing lists