All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corneliu ZUZU <czuzu@bitdefender.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>, xen-devel@lists.xen.org
Cc: Kevin Tian <kevin.tian@intel.com>,
	Tamas K Lengyel <tamas@tklengyel.com>, Keir Fraser <keir@xen.org>,
	Jan Beulich <jbeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCH v3 1/2] xen/x86: merge 2 hvm_event_... functions into 1
Date: Mon, 15 Feb 2016 19:40:33 +0200	[thread overview]
Message-ID: <56C20D91.9010305@bitdefender.com> (raw)
In-Reply-To: <56C18CAE.9050103@bitdefender.com>

On 2/15/2016 10:30 AM, Razvan Cojocaru wrote:
> On 02/15/2016 08:35 AM, Corneliu ZUZU wrote:
>> This patch merges almost identical functions hvm_event_int3 and
>> hvm_event_single_step into a single function called hvm_event_breakpoint.
>> Also fixes event.c file header comment in the process.
>>
>> Signed-off-by: Corneliu ZUZU <czuzu@bitdefender.com>
>> ---
>>   xen/arch/x86/hvm/event.c        | 108 +++++++++++++++++++---------------------
>>   xen/arch/x86/hvm/vmx/vmx.c      |  15 +++---
>>   xen/include/asm-x86/hvm/event.h |  11 ++--
>>   3 files changed, 67 insertions(+), 67 deletions(-)
> Looks good to me.
>
> Acked-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
>
>
> Thanks,
> Razvan
>

I forgot to ask: when getting an Acked-By response, should I include 
that patch in the next patch-series
or ommit it? I've done that w/ the first patch in the last patch-series, 
but IDK if I was correct to do so.

Thanks,
Corneliu.

  reply	other threads:[~2016-02-15 17:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15  6:35 [PATCH v3 0/2] Vm-events: move monitor vm-events code to common-side Corneliu ZUZU
2016-02-15  6:35 ` [PATCH v3 1/2] xen/x86: merge 2 hvm_event_... functions into 1 Corneliu ZUZU
2016-02-15  8:30   ` Razvan Cojocaru
2016-02-15 17:40     ` Corneliu ZUZU [this message]
2016-02-15 17:47       ` Tamas K Lengyel
2016-02-15 17:54         ` Corneliu ZUZU
2016-02-15 18:10           ` Razvan Cojocaru
2016-02-15  6:37 ` [PATCH v3 2/2] xen/vm-events: Move parts of monitor_domctl code to common-side Corneliu ZUZU
2016-02-15  8:46   ` Corneliu ZUZU
2016-02-15 11:41   ` Jan Beulich
2016-02-15 12:14     ` Corneliu ZUZU
2016-02-15 12:44       ` Jan Beulich
2016-02-15 13:29         ` Corneliu ZUZU
2016-02-15 14:08           ` Jan Beulich
2016-02-15 16:15             ` Tamas K Lengyel
2016-02-15 16:28             ` Corneliu ZUZU
2016-02-15 16:44               ` Jan Beulich
2016-02-15 16:51                 ` Tamas K Lengyel
2016-02-15 16:59                   ` Corneliu ZUZU
2016-02-15 12:21     ` Corneliu ZUZU
2016-02-15 12:25     ` Stefano Stabellini
2016-02-15 12:42       ` Corneliu ZUZU

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=56C20D91.9010305@bitdefender.com \
    --to=czuzu@bitdefender.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=kevin.tian@intel.com \
    --cc=rcojocaru@bitdefender.com \
    --cc=tamas@tklengyel.com \
    --cc=xen-devel@lists.xen.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.