All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Linda <lindaj@jma3.com>, Wei Liu <wei.liu2@citrix.com>
Cc: lars.kurth.xen@gmail.com, ian.jackson@citrix.com,
	stefano.stabellini@eu.citrix.com, ian.campbell@citrix.com,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] new functions libxl_bitmap_{or,and}
Date: Tue, 14 Apr 2015 13:28:48 +0100	[thread overview]
Message-ID: <552D0800.2050801@citrix.com> (raw)
In-Reply-To: <552D04B5.7050302@jma3.com>

Hi Linda,

Hi Linda,

On 14/04/15 13:14, Linda wrote:
> On 4/14/2015 3:19 AM, Wei Liu wrote:
>> Thanks, we're getting there. If my comments confuse you please just ask
>> for clarification.
>>
>> There is no need to change the subject line.  However, it would be
>> useful if you have some kind of version number in you subject line. That
>> is
>>
>>     [PATCH vX] libxl: provide libxl_bimap_{and,or}
>>
>> You can do this by supplying --subject-prefix= to git format-patch
>>
>>     git format-patch -1 --subject-prefix="[PATCH vX]" ...
> What version do you want me to use at this point?  I've sort of lost
> count, since many changes have been style changes.

IIRC, this is the v3, so the next will be v4.

> I am assuming you usually reserve new versions for substantive changes?

The version number should be incremented every time you send a new
version of the patch to the mailing list.

>>
>> where X refers to your version number.
>>
>> On Mon, Apr 13, 2015 at 01:47:18AM -0600, Linda Jacobson wrote:
>>> provide logical and and or of two bitmaps
>>>
>> And the SoB line should be here.
> What does SoB stand for in this context?

Signed-off-by.

As said on a previous mail, everything after "---" will be dropped when
the committer will apply your patch to the tree. So your SoB will
disappear too.

You have to move it before the "---"

>>
>>> ---
>>>
>>> v.1  updated comments and format
>>> v.2  rewrote bitmap functions to manipulate bytes not bits
>>>
>>> Signed-off-by: Linda Jacobson <lindaj@jma3.com>

[..]

>>
>>> +int libxl_bitmap_or(libxl_ctx *ctx, libxl_bitmap *or_map,
>>> +                    libxl_bitmap *map1, libxl_bitmap *map2)
>> Actually I think you need to constify map1 and map2. I.e.
>>
>>                         const libxl_bitmap *map1,
>>                const libxl_bitmap *map2)
> How come?  Out of curiosity.

You know that the 2 bitmaps won't be modified within function.
Constifying them will allow the compiler to catch any attempt to modify
the content of the bitmap.

Regards,

-- 
Julien Grall

      reply	other threads:[~2015-04-14 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13  7:47 [PATCH] new functions libxl_bitmap_{or,and} Linda Jacobson
2015-04-14  9:19 ` Wei Liu
2015-04-14 12:14   ` Linda
2015-04-14 12:28     ` Julien Grall [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=552D0800.2050801@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=lars.kurth.xen@gmail.com \
    --cc=lindaj@jma3.com \
    --cc=stefano.stabellini@eu.citrix.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.