From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCHv1 0/3] xen/events: remove some unused/unnecessary code
Date: Mon, 17 Feb 2014 14:27:47 -0500 [thread overview]
Message-ID: <530262B3.5000603@oracle.com> (raw)
In-Reply-To: <1392659118-32593-1-git-send-email-david.vrabel@citrix.com>
On 02/17/2014 12:45 PM, David Vrabel wrote:
> Remove some unused and unnecessary event channel code.
>
> David
>
I'd probably leave the blank line in bind_virq_to_irq() (second patch).
Other than that
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
prev parent reply other threads:[~2014-02-17 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 17:45 [PATCHv1 0/3] xen/events: remove some unused/unnecessary code David Vrabel
2014-02-17 17:45 ` [PATCH 1/3] xen/events: remove the unused resend_irq_on_evtchn() David Vrabel
2014-02-17 17:45 ` [PATCH 2/3] xen/events: remove unnecessary call to bind_evtchn_to_cpu() David Vrabel
2014-02-17 17:45 ` [PATCH 3/3] xen/xenbus: remove unused xenbus_bind_evtchn() David Vrabel
2014-02-17 19:27 ` Boris Ostrovsky [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=530262B3.5000603@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.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 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).