[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1321871797.3664.376.camel@zakaz.uk.xensource.com>
Date: Mon, 21 Nov 2011 10:36:36 +0000
From: Ian Campbell <Ian.Campbell@...rix.com>
To: ANNIE LI <annie.li@...cle.com>
CC: "jeremy@...p.org" <jeremy@...p.org>,
"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
"konrad.wilk@...cle.com" <konrad.wilk@...cle.com>,
"kurt.hackel@...cle.com" <kurt.hackel@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Paul Durrant <Paul.Durrant@...rix.com>
Subject: Re: [Xen-devel] [PATCH 1/3] xen/granttable: Introducing grant table
V2 stucture
On Mon, 2011-11-21 at 09:51 +0000, ANNIE LI wrote:
> This patch changes two places from the last one,
> * removing gnttab_v1_ops
> * change update_grant_entry_v1 into gnttab_update_entry_v1
The attached patch didn't have those changes.
Ian.
>
> Thanks
> Annie
>
> On 2011-11-19 0:04, Ian Campbell wrote:
> >>>> +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?
> > I think so. Similarly for the v2 variant.
> >
> > Ian.
> >
> >
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists