All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Linda Jacobson <lindaj@jma3.com>, xen-devel@lists.xen.org
Cc: lars.kurth.xen@gmail.com, wei.liu2@citrix.com
Subject: Re: [PATCH 2/2] update definition of libxl_bitmap_{or, and}
Date: Sat, 11 Apr 2015 21:32:38 +0100	[thread overview]
Message-ID: <552984E6.1000907@citrix.com> (raw)
In-Reply-To: <1428726307-31504-2-git-send-email-lindaj@jma3.com>

Hi Linda,

As said on the previous patch, it's not necessary to send another patch 
in order to fix the previous one. Can you merge them?

Regards,

On 11/04/2015 05:25, Linda Jacobson wrote:
> Fixed a comment that included a reference to a function that was
> not included with these changes.
>
> Signed-off-by: Linda Jacobson <lindaj@jma3.com>
> ---
>   tools/libxl/libxl_utils.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/libxl/libxl_utils.h b/tools/libxl/libxl_utils.h
> index 0b6480d..4852127 100644
> --- a/tools/libxl/libxl_utils.h
> +++ b/tools/libxl/libxl_utils.h
> @@ -91,7 +91,7 @@ void libxl_bitmap_set(libxl_bitmap *bitmap, int bit);
>   void libxl_bitmap_reset(libxl_bitmap *bitmap, int bit);
>   int libxl_bitmap_count_set(const libxl_bitmap *bitmap);
>   char *libxl_bitmap_to_hex_string(libxl_ctx *ctx, const libxl_bitmap *bitmap);
> -/* or, and and xor functions for two bitmaps
> +/* or and and functions for two bitmaps
>    */
>   int libxl_bitmap_or(libxl_ctx *ctx, libxl_bitmap *or_map,
>                       libxl_bitmap *map1, libxl_bitmap *map2);
>

-- 
Julien Grall

  reply	other threads:[~2015-04-11 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11  4:25 [PATCH 2/2] update definition of libxl_bitmap_{or, and} Linda Jacobson
2015-04-11 20:32 ` Julien Grall [this message]
2015-04-11 20:53   ` Linda

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=552984E6.1000907@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=lars.kurth.xen@gmail.com \
    --cc=lindaj@jma3.com \
    --cc=wei.liu2@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 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.