From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] gnttab: drop unused GNTCOPY_can_fail
Date: Mon, 10 Jun 2013 13:22:59 +0100 [thread overview]
Message-ID: <CDDB83B3.290BB%keir.xen@gmail.com> (raw)
In-Reply-To: <51B5DF4902000078000DCA1C@nat28.tlf.novell.com>
On 10/06/2013 13:14, "Jan Beulich" <JBeulich@suse.com> wrote:
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Keir Fraser <keir@xen.org>
> --- a/xen/include/public/grant_table.h
> +++ b/xen/include/public/grant_table.h
> @@ -449,8 +449,6 @@ DEFINE_XEN_GUEST_HANDLE(gnttab_transfer_
> #define GNTCOPY_source_gref (1<<_GNTCOPY_source_gref)
> #define _GNTCOPY_dest_gref (1)
> #define GNTCOPY_dest_gref (1<<_GNTCOPY_dest_gref)
> -#define _GNTCOPY_can_fail (2)
> -#define GNTCOPY_can_fail (1<<_GNTCOPY_can_fail)
>
> struct gnttab_copy {
> /* IN parameters. */
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-06-10 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 12:14 [PATCH] gnttab: drop unused GNTCOPY_can_fail Jan Beulich
2013-06-10 12:22 ` Keir Fraser [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=CDDB83B3.290BB%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.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.