public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	 Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	 Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org,  "H. Peter Anvin" <hpa@zytor.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Liao Yuanhong <liaoyuanhong@vivo.com>
Subject: Re: [PATCH] KVM: x86: hyper-v: Use guard() instead of mutex_lock() to simplify code
Date: Tue, 16 Sep 2025 13:01:51 -0700	[thread overview]
Message-ID: <aMnCL3SdKcQP0ZUO@google.com> (raw)
In-Reply-To: <175798207153.624508.1085968130364515751.b4-ty@google.com>

On Mon, Sep 15, 2025, Sean Christopherson wrote:
> 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

This one also got affected by the force push for an unrelated commit, new hash:

      https://github.com/kvm-x86/linux/commit/cbd860293d13

      reply	other threads:[~2025-09-16 20:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 13:16 [PATCH] KVM: x86: hyper-v: Use guard() instead of mutex_lock() to simplify code Liao Yuanhong
2025-09-16  0:25 ` Sean Christopherson
2025-09-16 20:01   ` Sean Christopherson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aMnCL3SdKcQP0ZUO@google.com \
    --to=seanjc@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=liaoyuanhong@vivo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox