From: Thomas Gleixner <tglx@linutronix.de>
To: Christoph Egger <siccegge@cs.fau.de>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Linus Walleij <linus.walleij@stericsson.com>,
Jon Hunter <jon-hunter@ti.com>,
linux-kernel@vger.kernel.org,
vamos@i4.informatik.uni-erlangen.de
Subject: Re: [PATCH] transitional config CONFIG_GENERIC_CLOCKEVENTS
Date: Wed, 26 May 2010 17:50:34 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1005261750110.2995@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.1005261708420.2995@localhost.localdomain>
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
prev parent reply other threads:[~2010-05-26 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 13:44 Christoph Egger
2010-05-26 13:55 ` Christoph Hellwig
2010-05-26 13:56 ` Thomas Gleixner
2010-05-26 14:57 ` Christoph Egger
2010-05-26 15:13 ` Thomas Gleixner
2010-05-26 15:50 ` Thomas Gleixner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.00.1005261750110.2995@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=jon-hunter@ti.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=siccegge@cs.fau.de \
--cc=vamos@i4.informatik.uni-erlangen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®