From: pr-tracker-bot@kernel.org
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
kvm@vger.kernel.org, mst@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, eli@mellanox.com,
elic@nvidia.com, lingshan.zhu@intel.com
Subject: Re: [GIT PULL] virtio: last minute fixes
Date: Tue, 29 Sep 2020 17:44:08 +0000 [thread overview]
Message-ID: <160140144806.29614.17781182961923244998.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20200929035034-mutt-send-email-mst@kernel.org>
The pull request you sent on Tue, 29 Sep 2020 03:50:34 -0400:
> https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1ccfa66d94cf65d3e89eeb95676a03e8f90edd99
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
WARNING: multiple messages have this Message-ID (diff)
From: pr-tracker-bot@kernel.org
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org, mst@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, eli@mellanox.com,
elic@nvidia.com, Linus Torvalds <torvalds@linux-foundation.org>,
lingshan.zhu@intel.com
Subject: Re: [GIT PULL] virtio: last minute fixes
Date: Tue, 29 Sep 2020 17:44:08 +0000 [thread overview]
Message-ID: <160140144806.29614.17781182961923244998.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20200929035034-mutt-send-email-mst@kernel.org>
The pull request you sent on Tue, 29 Sep 2020 03:50:34 -0400:
> https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1ccfa66d94cf65d3e89eeb95676a03e8f90edd99
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2020-09-29 17:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 7:50 [GIT PULL] virtio: last minute fixes Michael S. Tsirkin
2020-09-29 7:50 ` Michael S. Tsirkin
2020-09-29 17:44 ` pr-tracker-bot [this message]
2020-09-29 17:44 ` pr-tracker-bot
2021-04-22 22:20 Michael S. Tsirkin
2021-04-22 22:20 ` Michael S. Tsirkin
2021-04-22 23:30 ` pr-tracker-bot
2021-04-22 23:30 ` pr-tracker-bot
2021-10-27 20:08 Michael S. Tsirkin
2021-10-27 20:08 ` Michael S. Tsirkin
2021-10-28 17:25 ` pr-tracker-bot
2021-10-28 17:25 ` pr-tracker-bot
2022-03-07 11:03 Michael S. Tsirkin
2022-03-07 11:03 ` Michael S. Tsirkin
2022-03-07 19:47 ` pr-tracker-bot
2022-03-07 19:47 ` pr-tracker-bot
2023-04-10 9:59 Michael S. Tsirkin
2023-04-10 9:59 ` Michael S. Tsirkin
2023-04-10 21:21 ` pr-tracker-bot
2023-04-10 21:21 ` pr-tracker-bot
2023-10-23 5:02 Michael S. Tsirkin
2023-10-23 5:02 ` Michael S. Tsirkin
2023-10-23 18:03 ` pr-tracker-bot
2023-10-23 18:03 ` pr-tracker-bot
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=160140144806.29614.17781182961923244998.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=eli@mellanox.com \
--cc=elic@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.