From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>,
xen-devel@lists.xenproject.org
Cc: keir@xen.org, jbeulich@suse.com
Subject: Re: [PATCH] x86/hvm: Fix non-onchangeonly CR write events logic
Date: Wed, 12 Aug 2015 18:45:13 +0100 [thread overview]
Message-ID: <55CB8629.3010709@citrix.com> (raw)
In-Reply-To: <1439398804-8524-1-git-send-email-rcojocaru@bitdefender.com>
On 12/08/15 18:00, Razvan Cojocaru wrote:
> hvm_event_crX() already returns a bool_t to tell us whether an
> event will be sent out or not, so the extra check that value != old
> is not only useless, but also prevents non-onchangeonly events from
> being sent.
>
> Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
I presume this is a 4.6 candidate? If so, you need to CC the release
manager as we are into the RC's
~Andrew
next prev parent reply other threads:[~2015-08-12 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 17:00 [PATCH] x86/hvm: Fix non-onchangeonly CR write events logic Razvan Cojocaru
2015-08-12 17:45 ` Andrew Cooper [this message]
2015-08-12 17:48 ` Razvan Cojocaru
2015-08-13 9:23 ` Wei Liu
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=55CB8629.3010709@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=rcojocaru@bitdefender.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 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.