[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090610150314.c1593e6e.akpm@linux-foundation.org>
Date: Wed, 10 Jun 2009 15:03:14 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
tglx@...utronix.de, hpa@...or.com, jeremy@...p.org
Subject: Re: [GIT PULL] x86/xen changes for v2.6.31
On Wed, 10 Jun 2009 23:54:23 +0200
Ingo Molnar <mingo@...e.hu> wrote:
> Linus,
>
> Please pull the latest x86-xen-for-linus git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git x86-xen-for-linus
>
> ...
>
> Jeremy Fitzhardinge (32):
> mm: disable preemption in apply_to_pte_range
> ...
> mm: allow preemption in apply_to_pte_range
I think these cancel each other out, don't they?
It's strange that I cant find them in linux-next, whereas the others:
> x86/paravirt: use percpu_ rather than __get_cpu_var
> xen: disable preempt for leave_lazy_mmu
> xen: separate p2m allocation from setting
are present in linux-next. Perhaps Stephen's merge process cancelled
the self-cancelling patches altogether.
--
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