Changes inside powerpc files are fine. Obviously powerpc-specific changes
inside common files are usually fine. Changes to locking protocols in common
files (e.g., changed usage of mmap_sem in privcmd.c) is *not* fine. Please
post patches for that kind of thing.
-- Keir
On 6/7/07 22:29, Hollis
The xenppc-unstable is already merged and fixed.
-- Keir
On 5/3/07 19:24, Hollis Blanchard [EMAIL PROTECTED] wrote:
There are two patches that touch common code:
* Add a guest_physmap hook for max_mem changes. We've finally
gotten around to removing a hack we've carried in
On Fri, 2007-03-02 at 17:52 -0600, Hollis Blanchard wrote:
Hi Keir, could you please pull from
http://xenbits.xensource.com/ext/xenppc-unstable-merge.hg ?
There are two patches that touch common code:
* Add a guest_physmap hook for max_mem changes. We've finally
gotten around
On Fri, 2007-02-09 at 14:58 -0600, Hollis Blanchard wrote:
Hi Keir, please pull from
http://xenbits.xensource.com/ext/xenppc-unstable-merge.hg
Among the PPC updates are the two libelf patches I sent separately.
Hi Keir, any comments on this?
--
Hollis Blanchard
IBM Linux Technology Center
On Wed, 2007-02-14 at 18:55 +, Keir Fraser wrote:
On 14/2/07 16:44, Hollis Blanchard [EMAIL PROTECTED] wrote:
On Fri, 2007-02-09 at 14:58 -0600, Hollis Blanchard wrote:
Hi Keir, please pull from
http://xenbits.xensource.com/ext/xenppc-unstable-merge.hg
Among the PPC updates are
On Sat, 2006-12-09 at 13:53 +, Keir Fraser wrote:
Just check all these patches into the PPC tree and I’ll merge them
into unstable with the rest. I always check the diff when I merge
anyway.
OK, they are now committed.
Please hg pull http://xenbits.xensource.com/xenppc-unstable-merge.hg
