[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5201ED01.7000803@linux.vnet.ibm.com>
Date: Wed, 07 Aug 2013 12:15:21 +0530
From: Raghavendra K T <raghavendra.kt@...ux.vnet.ibm.com>
To: "H. Peter Anvin" <hpa@...or.com>
CC: gleb@...hat.com, mingo@...hat.com, jeremy@...p.org, x86@...nel.org,
konrad.wilk@...cle.com, pbonzini@...hat.com,
linux-doc@...r.kernel.org, habanero@...ux.vnet.ibm.com,
xen-devel@...ts.xensource.com, peterz@...radead.org,
mtosatti@...hat.com, stefano.stabellini@...citrix.com,
andi@...stfloor.org, attilio.rao@...rix.com, ouyang@...pitt.edu,
gregkh@...e.de, agraf@...e.de, chegu_vinod@...com,
torvalds@...ux-foundation.org, avi.kivity@...il.com,
tglx@...utronix.de, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, riel@...hat.com, drjones@...hat.com,
virtualization@...ts.linux-foundation.org,
srivatsa.vaddagiri@...il.com
Subject: Re: [PATCH V12 0/14] Paravirtualized ticket spinlocks
On 08/07/2013 10:18 AM, H. Peter Anvin wrote:
>> Please let me know, if I should rebase again.
>>
>
> tip:master is not a stable branch; it is more like linux-next. We need
> to figure out which topic branches are dependencies for this set.
Okay. I 'll start looking at the branches that would get affected.
(Xen, kvm are obvious ones).
Please do let me know the branches I might have to check for.
--
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