From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755251Ab0EZPus (ORCPT ); Wed, 26 May 2010 11:50:48 -0400 Received: from www.tglx.de ([62.245.132.106]:45811 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754870Ab0EZPuq (ORCPT ); Wed, 26 May 2010 11:50:46 -0400 Date: Wed, 26 May 2010 17:50:34 +0200 (CEST) From: Thomas Gleixner To: Christoph Egger cc: Ralf Baechle , Linus Walleij , Jon Hunter , linux-kernel@vger.kernel.org, vamos@i4.informatik.uni-erlangen.de Subject: Re: [PATCH] transitional config CONFIG_GENERIC_CLOCKEVENTS In-Reply-To: Message-ID: References: <20100526134415.GD7508@faui49.informatik.uni-erlangen.de> <20100526145700.GA5475@faui48a.informatik.uni-erlangen.de> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 26 May 2010, Thomas Gleixner wrote: > > Are you referring to some out-of-tree architectures? I've > > verified the string GENERIC_CLOCKEVENTS_MIGR is only appearing at this > > single spot in kconfig and nowhere else in code/Kconfig in my > > up-to-date linux tree. > > No. I'm referring to in tree archs which do not use the clock events > at all yet. The MIGR symbol allows them to do a step by step > conversion which builds the generic clock events stuff first before > switching over to use them. That's why it was created in the first > place and it has been proven useful when doing such work. So I'd > rather see it stay until all archs actually use the generic framework. > > But yes, we can apply your patch and just let them select > GENERIC_CLOCKEVENTS_BUILD instead. Gah, we can't. tglx