|author||Thomas Gleixner <email@example.com>||2012-05-21 23:16:18 +0200|
|committer||Thomas Gleixner <firstname.lastname@example.org>||2012-05-21 23:43:46 +0200|
timers: Fixup the Kconfig consolidation fallout
Sigh, I missed to check which architecture Kconfig files actually include the core Kconfig file. There are a few which did not. So we broke them. Instead of adding the includes to those, we are better off to move the include to init/Kconfig like we did already with irqs and others. This does not change anything for the architectures using the old style periodic timer mode. It just solves the build wreckage there. For those architectures which use the clock events infrastructure it moves the include of the core Kconfig file to "General setup" which is a way more logical place than having it at random locations specified by the architecture specific Kconfigs. Reported-by: Ingo Molnar <email@example.com> Cc: Anna-Maria Gleixner <firstname.lastname@example.org> Signed-off-by: Thomas Gleixner <email@example.com>
Diffstat (limited to 'arch/microblaze/Kconfig')
1 files changed, 0 insertions, 2 deletions
diff --git a/arch/microblaze/Kconfig b/arch/microblaze/Kconfig
index 3e786ac9a65..83460468998 100644
@@ -74,8 +74,6 @@ source "arch/microblaze/platform/Kconfig.platform"
menu "Processor type and features"