mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Egger <siccegge@cs.fau.de>
To: Thomas Gleixner <tglx@linutronix.de>,
	Ralf Baechle <ralf@linux-mips.org>,
	Linus Walleij <linus.walleij@stericsson.com>,
	Jon Hunter <jon-hunter@ti.com>,
	linux-kernel@vger.kernel.org
Cc: vamos@i4.informatik.uni-erlangen.de
Subject: [PATCH] transitional config CONFIG_GENERIC_CLOCKEVENTS
Date: Wed, 26 May 2010 15:44:15 +0200	[thread overview]
Message-ID: <20100526134415.GD7508@faui49.informatik.uni-erlangen.de> (raw)

Hi all!

	As part of the VAMOS[0] research project at the University of
Erlangen we are looking at multiple integrity errors in linux'
configuration system.

	This was an aid for a transition finished 2007 so not
necessary for some time now, ready for removal.

	Please keep me informed of this patch getting confirmed /
merged so we can keep track of it.

Regards

	Christoph Egger

[0] http://vamos1.informatik.uni-erlangen.de/

----
>From c8092c26246db170d509dd3424e65e87e67c5a8a Mon Sep 17 00:00:00 2001
From: Christoph Egger <siccegge@cs.fau.de>
Date: Fri, 21 May 2010 17:24:01 +0200
Subject: [PATCH 1/2] Remove transitional, dead GENERIC_CLOCKEVENTS_MIGR

GENERIC_CLOCKEVENTS_MIGR was introduced to facilate transition to the
new codebase which was finished 2007 with
b8ce33590687888ebb900d09557b8807c4539022. However the config Item and
a tiny bit of code wasn't removed back then which is adressed by this
patch.

One might consider getting rid of GENERIC_CLOCKEVENTS_BUILD
alltogether however this patch is limited to changes to affecting the
actual build process in any way.

Signed-off-by: Christoph Egger <siccegge@cs.fau.de>
---
 include/linux/clockchips.h |    4 ----
 kernel/time/Kconfig        |    2 +-
 2 files changed, 1 insertions(+), 5 deletions(-)

diff --git a/include/linux/clockchips.h b/include/linux/clockchips.h
index fc53492..3ad8331 100644
--- a/include/linux/clockchips.h
+++ b/include/linux/clockchips.h
@@ -139,11 +139,7 @@ clockevents_calc_mult_shift(struct clock_event_device *ce, u32 freq, u32 minsec)
 				      freq, minsec);
 }
 
-#ifdef CONFIG_GENERIC_CLOCKEVENTS
 extern void clockevents_notify(unsigned long reason, void *arg);
-#else
-# define clockevents_notify(reason, arg) do { } while (0)
-#endif
 
 #else /* CONFIG_GENERIC_CLOCKEVENTS_BUILD */
 
diff --git a/kernel/time/Kconfig b/kernel/time/Kconfig
index 95ed429..18ed376 100644
--- a/kernel/time/Kconfig
+++ b/kernel/time/Kconfig
@@ -25,5 +25,5 @@ config HIGH_RES_TIMERS
 config GENERIC_CLOCKEVENTS_BUILD
 	bool
 	default y
-	depends on GENERIC_CLOCKEVENTS || GENERIC_CLOCKEVENTS_MIGR
+	depends on GENERIC_CLOCKEVENTS
 
-- 
1.6.3.3










             reply	other threads:[~2010-05-26 13:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 13:44 Christoph Egger [this message]
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

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=20100526134415.GD7508@faui49.informatik.uni-erlangen.de \
    --to=siccegge@cs.fau.de \
    --cc=jon-hunter@ti.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=tglx@linutronix.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®