linux-next.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>
Subject: linux-next: Fixes tag needs some work in the kvm tree
Date: Wed, 4 Dec 2019 23:50:20 +1100	[thread overview]
Message-ID: <20191204235020.2e8e39bf@canb.auug.org.au> (raw)

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

Hi all,

In commit

  433f4ba19041 ("KVM: x86: fix out-of-bounds write in KVM_GET_EMULATED_CPUID (CVE-2019-19332)")

Fixes tag

  Fixes: 84cffe499b94 ("kvm: Emulate MOVBE", 2013-10-29)

has these problem(s):

  - Unexpected trailing date
    Just use
	git log -1 --format='Fixes: %h ("%s")'

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2019-12-04 12:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 12:50 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-09 21:31 linux-next: Fixes tag needs some work in the kvm tree Stephen Rothwell
2022-07-20 22:05 Stephen Rothwell
2022-05-22  0:49 Stephen Rothwell
2022-01-19 11:49 Stephen Rothwell
2021-09-06 21:48 Stephen Rothwell
2021-08-19 22:20 Stephen Rothwell
2021-06-21 22:18 Stephen Rothwell
2021-06-21 23:37 ` Paolo Bonzini
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-02-04 20:16 Stephen Rothwell
2020-03-16 20:36 Stephen Rothwell
2020-01-24  3:13 Stephen Rothwell
2019-02-16  7:34 Stephen Rothwell
2019-02-20  7:02 ` Yu Zhang

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=20191204235020.2e8e39bf@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --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 \
    /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).