[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1005261750110.2995@localhost.localdomain>
Date: Wed, 26 May 2010 17:50:34 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Christoph Egger <siccegge@...fau.de>
cc: Ralf Baechle <ralf@...ux-mips.org>,
Linus Walleij <linus.walleij@...ricsson.com>,
Jon Hunter <jon-hunter@...com>, linux-kernel@...r.kernel.org,
vamos@...informatik.uni-erlangen.de
Subject: Re: [PATCH] transitional config CONFIG_GENERIC_CLOCKEVENTS
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
--
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