kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>, KVM <kvm@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Wanpeng Li <wanpengli@tencent.com>,
	Haiwei Li <lihaiwei.kernel@gmail.com>
Subject: linux-next: Fixes tags need some work in the kvm-fixes tree
Date: Wed, 4 Mar 2020 07:39:38 +1100	[thread overview]
Message-ID: <20200304073938.73ac724d@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 743 bytes --]

Hi all,

In commit

  aaca21007ba1 ("KVM: SVM: Fix the svm vmexit code for WRMSR")

Fixes tag

  Fixes: 1e9e2622a149 ("KVM: VMX: FIXED+PHYSICAL mode single target IPI fastpath", 2019-11-21)

has these problem(s):

  - Subject does not match target commit subject
    Just use
	git log -1 --format='Fixes: %h ("%s")'

In commit

  9a11997e757b ("KVM: X86: Fix dereference null cpufreq policy")

Fixes tag

  Fixes: aaec7c03de (KVM: x86: avoid useless copy of cpufreq policy)

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
    or later) just making sure it is not set (or set to "auto").

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2020-03-03 20:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 20:39 Stephen Rothwell [this message]
2020-08-02 11:11 linux-next: Fixes tags need some work in the kvm-fixes tree Stephen Rothwell
2022-04-11 22:00 Stephen Rothwell
2022-04-12  1:07 ` Heiko Stübner
2022-04-21 21:50 Stephen Rothwell
2022-04-21 21:56 ` Atish Kumar Patra

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=20200304073938.73ac724d@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=kvm@vger.kernel.org \
    --cc=lihaiwei.kernel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=wanpengli@tencent.com \
    /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;
as well as URLs for NNTP newsgroup(s).