Hi Dave, The fix to the allocator depends on some earlier patches I have sent out. Shall I put all of them in one big patch? Or just point out which earlier patches it depends on? The following is an excerpt from my series-file. Do the patch-names survive the publication by email somewhere?
stdext-fun_mapext_opt mlvm-refactor fun-application listext-take-tails opt-join allocator-fix-zero-alloc Matthias. -----Original Message----- From: Dave Scott Sent: 08 February 2010 13:29 To: Matthias Goergens; [email protected] Subject: RE: [Xen-API] [PATCH] Makes the allocator more robust by enabling allocation of 0 bytes Hi Matthias, I didn't manage to apply this patch. Perhaps I'm missing an intermediate patch? Could you send me another version which applies to the current tip of the repo? Thanks, Dave > -----Original Message----- > From: [email protected] [mailto:xen-api- > [email protected]] On Behalf Of Matthias Görgens > Sent: 02 February 2010 16:22 > To: [email protected] > Subject: [Xen-API] [PATCH] Makes the allocator more robust by enabling > allocation of 0 bytes > > `normalize' and `alloc_specified_area' no longer get confused by 0 byte > allocations. > > Signed-off-by: Matthias Goergens <[email protected]> > (Mercurial doesn't like Umlaute.) > > > mlvm/allocator.ml | 66 ++++++++++++++++++-------------- > 1 files changed, 37 insertions(+), 29 deletions(-) >
_______________________________________________ xen-api mailing list [email protected] http://lists.xensource.com/mailman/listinfo/xen-api
