From: Greg KH <gregkh@linux-foundation.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, rkrcmar@redhat.com, kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM changes for Linux 4.20-rc5
Date: Fri, 21 Sep 2018 15:55:34 +0200 [thread overview]
Message-ID: <20180921135534.GB13900@kroah.com> (raw)
In-Reply-To: <1537532067-42759-1-git-send-email-pbonzini@redhat.com>
On Fri, Sep 21, 2018 at 02:14:27PM +0200, Paolo Bonzini wrote:
> Greg,
>
> The following changes since commit 7876320f88802b22d4e2daf7eb027dd14175a0f8:
>
> Linux 4.19-rc4 (2018-09-16 11:52:37 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
No signed tag? You did that for the last pull request you sent to
Linus. Any reason you didn't do that here?
Care to fix that up and resend?
thanks,
greg k-h
next prev parent reply other threads:[~2018-09-21 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 12:14 [GIT PULL] KVM changes for Linux 4.20-rc5 Paolo Bonzini
2018-09-21 12:16 ` Paolo Bonzini
2018-09-21 13:55 ` Greg KH [this message]
2018-09-21 14:05 ` Paolo Bonzini
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=20180921135534.GB13900@kroah.com \
--to=gregkh@linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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