From: pr-tracker-bot@kernel.org
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
rkrcmar@redhat.com, kvm@vger.kernel.org
Subject: Re: [GIT PULL] Second batch of KVM changes for 5.3 merge window
Date: Sat, 20 Jul 2019 18:40:26 +0000 [thread overview]
Message-ID: <156364802618.20023.14003615157799136575.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <1563622987-4738-1-git-send-email-pbonzini@redhat.com>
The pull request you sent on Sat, 20 Jul 2019 13:43:07 +0200:
> https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/07ab9d5bc53d7fe84047be1d403566123ab9cfaa
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/prtracker
prev parent reply other threads:[~2019-07-20 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 11:43 [GIT PULL] Second batch of KVM changes for 5.3 merge window Paolo Bonzini
2019-07-20 18:40 ` pr-tracker-bot [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=156364802618.20023.14003615157799136575.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).