From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-arm-msm-owner@vger.kernel.org>
Received: from wolverine02.qualcomm.com ([199.106.114.251]:32095 "EHLO
	wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1757196Ab0EGSYP (ORCPT
	<rfc822;linux-arm-msm@vger.kernel.org>);
	Fri, 7 May 2010 14:24:15 -0400
Subject: Re: MSM PMU Support in Commit ee3c454b
From: Daniel Walker <dwalker@codeaurora.org>
In-Reply-To: <20100507181543.GC7887@n2100.arm.linux.org.uk>
References: <000101caee07$104acdc0$30e06940$@deacon@arm.com>
	 <20100507181543.GC7887@n2100.arm.linux.org.uk>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 07 May 2010 11:24:07 -0700
Message-ID: <1273256647.3542.45.camel@c-dwalke-linux.qualcomm.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-arm-msm-owner@vger.kernel.org
List-ID: <linux-arm-msm.vger.kernel.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Will Deacon <will.deacon@arm.com>, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org

On Fri, 2010-05-07 at 19:15 +0100, Russell King - ARM Linux wrote:
> Maybe I'll just keep the devel-stable branch entirely separate until
> the devel stuff has been merged, and then MSM can be sorted at some
> point later.  This unfortunately means that devel-stable drops out of
> linux-next.  It also means that linux-next is at risk of missing the
> merge window... again.

Would it matter if you just did a revert on the MSM pmu patch ?

Daniel