From: Adrian Pop <apop@bitdefender.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
Tamas K Lengyel <tamas@tklengyel.com>,
Wei Liu <wei.liu2@citrix.com>, Jan Beulich <jbeulich@suse.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v2] x86/monitor: add support for descriptor access events
Date: Tue, 4 Apr 2017 14:46:16 +0300 [thread overview]
Message-ID: <20170404114616.GA19448@hel> (raw)
In-Reply-To: <4319870d-0259-903f-8790-40f84756f331@bitdefender.com>
On Tue, Apr 04, 2017 at 01:52:24PM +0300, Razvan Cojocaru wrote:
> You've forgotten Wei Liu's ack for the first version of the patch.
>
> For the vm_event bits:
>
> Acked-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
Okay, will include them next time. Thanks!
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-04-04 11:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 9:57 [PATCH v2] x86/monitor: add support for descriptor access events Adrian Pop
2017-04-04 10:52 ` Razvan Cojocaru
2017-04-04 11:46 ` Adrian Pop [this message]
2017-04-04 13:23 ` Boris Ostrovsky
2017-04-04 13:45 ` Adrian Pop
2017-04-04 15:26 ` Andrew Cooper
2017-04-04 17:11 ` Adrian Pop
2017-04-05 7:13 ` Tian, Kevin
2017-04-05 14:26 ` Jan Beulich
2017-04-06 8:59 ` Adrian Pop
2017-04-06 9:20 ` Jan Beulich
2017-04-06 9:37 ` Adrian Pop
2017-04-06 14:09 ` Jan Beulich
2017-04-07 10:01 ` Adrian Pop
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=20170404114616.GA19448@hel \
--to=apop@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=rcojocaru@bitdefender.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tamas@tklengyel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).