From: Yu Zhang <yu.c.zhang@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>, KVM <kvm@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Sean Christopherson" <sean.j.christopherson@intel.com>
Subject: Re: linux-next: Fixes tag needs some work in the kvm tree
Date: Wed, 20 Feb 2019 15:02:33 +0800 [thread overview]
Message-ID: <20190220070233.lca2kquyzypofyh7@linux.intel.com> (raw)
In-Reply-To: <20190216183433.71b7cfa7@canb.auug.org.au>
Thanks for the notification, Stephen.
@Paolo, should I resubmit the patch to correct?
On Sat, Feb 16, 2019 at 06:34:33PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> aa8359972cfc ("KVM: x86/mmu: Differentiate between nr zapped and list unstable")
>
> Fixes tag
>
> Fixes: 54a4f0239f2e ("KVM: MMU: make kvm_mmu_zap_page() return
>
> has these problem(s):
>
> - Subject has leading but no trailing quotes
> Please do not split Fixes tags over more than one line
>
> In commit
>
> 4d3f8e4ff75e ("kvm: vmx: Fix typos in vmentry/vmexit control setting")
>
> Fixes tag
>
> Fixes: 'commit f99e3daf94ff ("KVM: x86: Add Intel PT virtualization work mode")'
>
> has these problem(s):
>
> - No SHA1 recognised
> The leading word 'commit' is unexpected and the surrounding single
> quotes likewise.
> Please just use
> git log -1 --format='Fixes: %h ("%s")' <SHA>
>
> --
> Cheers,
> Stephen Rothwell
B.R.
Yu
next prev parent reply other threads:[~2019-02-20 7:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 7:34 linux-next: Fixes tag needs some work in the kvm tree Stephen Rothwell
2019-02-20 7:02 ` Yu Zhang [this message]
2019-12-04 12:50 Stephen Rothwell
2020-01-24 3:13 Stephen Rothwell
2020-03-16 20:36 Stephen Rothwell
2021-02-04 20:16 Stephen Rothwell
2021-04-16 12:27 Stephen Rothwell
2021-04-16 12:38 ` Christian Borntraeger
2021-04-16 14:02 ` Paolo Bonzini
2021-04-16 14:58 ` Stephen Rothwell
2021-04-16 15:02 ` Christian Borntraeger
2021-06-21 22:18 Stephen Rothwell
2021-06-21 23:37 ` Paolo Bonzini
2021-08-19 22:20 Stephen Rothwell
2021-09-06 21:48 Stephen Rothwell
2022-01-19 11:49 Stephen Rothwell
2022-05-22 0:49 Stephen Rothwell
2022-07-20 22:05 Stephen Rothwell
2024-01-09 21:31 Stephen Rothwell
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=20190220070233.lca2kquyzypofyh7@linux.intel.com \
--to=yu.c.zhang@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=sfr@canb.auug.org.au \
/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).