All of lore.kernel.org
 help / color / mirror / Atom feed
From: annie li <annie.li@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "jeremy@goop.org" <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
	"kurt.hackel@oracle.com" <kurt.hackel@oracle.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Paul Durrant <Paul.Durrant@citrix.com>
Subject: Re: [PATCH 1/3] xen/granttable: Introducing grant table V2 stucture
Date: Sat, 19 Nov 2011 00:02:19 +0800	[thread overview]
Message-ID: <4EC6818B.3010904@oracle.com> (raw)
In-Reply-To: <1321613689.3664.305.camel@zakaz.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1121 bytes --]



On 2011-11-18 18:54, Ian Campbell wrote:
> Thanks for splitting these up.
>
> On Fri, 2011-11-18 at 10:07 +0000, ANNIE LI wrote:
>   
>> [...]
>>     
>
>   
>> return value
>> +        * by bit operations.
>> +        */
>> +       int (*query_foreign_access)(grant_ref_t);
>> +};
>> +
>> +static struct gnttab_ops gnttab_v1_ops;
>>     
>
> You don't actually need this forward declaration since the struct
> definition and usage are ordered correctly.
>
>   
Yes, you are right, this line should be removed.
>> +static struct gnttab_ops gnttab_v1_ops = {
>> +       .map_frames                     = gnttab_map_frames_v1,
>> +       .unmap_frames                   = gnttab_unmap_frames_v1,
>> +       .update_entry                   = update_grant_entry_v1,
>>     
>
> Any reason this one is not gnttab_foo?
>   
Actually no, just keep the original name of this function. I'd like to 
change it, maybe gnttab_update_entry_v1 is better?

Thanks
Annie
> Ian.
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>   

[-- Attachment #1.2: Type: text/html, Size: 2085 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-11-18 16:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 13:10 Improved patches of upstreaming grant table version 2 annie li
2011-11-16 13:23 ` [Xen-devel] " annie li
2011-11-16 13:48 ` [PATCH 1/3] xen/granttable: Introducing grant table V2 stucture annie.li
2011-11-17 10:35   ` Ian Campbell
2011-11-17 16:06     ` annie li
2011-11-17 16:29       ` Konrad Rzeszutek Wilk
2011-11-18  3:08         ` [Xen-devel] " ANNIE LI
2011-11-18  3:08           ` ANNIE LI
2011-11-17 16:55       ` Ian Campbell
2011-11-17 16:55         ` Ian Campbell
2011-11-18 10:07   ` [Xen-devel] " ANNIE LI
2011-11-18 10:54     ` Ian Campbell
2011-11-18 10:54       ` Ian Campbell
2011-11-18 16:02       ` annie li [this message]
2011-11-18 16:04         ` [Xen-devel] " Ian Campbell
2011-11-21  9:51           ` ANNIE LI
2011-11-21 10:36             ` Ian Campbell
2011-11-16 13:49 ` [PATCH 2/3] xen/granttable: Grant tables V2 implementation annie.li
2011-11-16 13:49   ` annie.li
2011-11-18 10:13   ` ANNIE LI
2011-11-18 11:02     ` Ian Campbell
2011-11-18 13:52       ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-11-18 14:00         ` Ian Campbell
2011-11-18 16:10           ` annie li
2011-11-18 18:05             ` Konrad Rzeszutek Wilk
2011-11-19  3:36               ` annie li
2011-11-21  9:51               ` ANNIE LI
2011-11-21 10:35                 ` Ian Campbell
2011-11-21 11:42                   ` annie li
2011-11-16 13:50 ` [PATCH 3/3] xen/granttable: Keep code format clean annie.li
2011-11-18 10:16   ` ANNIE LI

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=4EC6818B.3010904@oracle.com \
    --to=annie.li@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=kurt.hackel@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /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.