mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Tyler Baker <tyler.baker@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	rafael.j.wysocki@intel.com, John Stultz <john.stultz@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Kevin Hilman <khilman@linaro.org>
Subject: Re: Build regression in next-20150331
Date: Wed, 01 Apr 2015 01:03:52 +0200	[thread overview]
Message-ID: <1489627.zlEOcOu4fx@vostro.rjw.lan> (raw)
In-Reply-To: <CANMBJr68RVNgVpkDohyOeH=wd=UgKBCFeuveqiUyNcQ_7vendQ@mail.gmail.com>

On Tuesday, March 31, 2015 11:39:37 AM Tyler Baker wrote:
> Hi Thomas, Rafael,
> 
> I was notified this morning by the kernelci.org system that a new
> build error has been detected in next-20150331[0][1][2]. It seems that
> "clockevents: Remove CONFIG_GENERIC_CLOCKEVENTS_BUILD"
> c9439b1d6eb4ada5c2faf3970ac0d2bc4bd20e14 is the culprit.
> 
> Initially, I reported these failures to John Stultz and his response is below.
> 
> *snip*
> 
> I suspect we either need to enable GENERIC_CLOCKEVENTS on those three
> hardware types, or if that's not possible, rework the definitions.
> 
> Or something like (copy-paste whitespace corruption below.. only for
> reference, don't apply):
> 
> diff --git a/kernel/time/tick-internal.h b/kernel/time/tick-internal.h
> index 2a1563a..6da40c0 100644
> --- a/kernel/time/tick-internal.h
> +++ b/kernel/time/tick-internal.h
> @@ -107,12 +107,13 @@ static inline void tick_resume_broadcast(void) { }
>  static inline bool tick_resume_check_broadcast(void) { return false; }
>  static inline void tick_broadcast_init(void) { }
>  static inline int tick_broadcast_update_freq(struct
> clock_event_device *dev, u32 freq) { return -ENODEV; }
> -
> +#ifdef CONFIG_GENERIC_CLOCKEVENTS
>  /* Set the periodic handler in non broadcast mode */
>  static inline void tick_set_periodic_handler(struct
> clock_event_device *dev, int broadcast)
>  {
>         dev->event_handler = tick_handle_periodic;
>  }
> +#endif
>  #endif /* !BROADCAST */
> 
> *snip*
> 
> Any chance either of you can reproduce this issue on your end?

Can you please tell me if the appended patch helps?

Rafael


---
 kernel/time/tick-internal.h |    4 ++++
 1 file changed, 4 insertions(+)

Index: linux-pm/kernel/time/tick-internal.h
===================================================================
--- linux-pm.orig/kernel/time/tick-internal.h
+++ linux-pm/kernel/time/tick-internal.h
@@ -107,11 +107,15 @@ static inline bool tick_resume_check_bro
 static inline void tick_broadcast_init(void) { }
 static inline int tick_broadcast_update_freq(struct clock_event_device *dev, u32 freq) { return -ENODEV; }
 
+#ifdef CONFIG_GENERIC_CLOCKEVENTS
 /* Set the periodic handler in non broadcast mode */
 static inline void tick_set_periodic_handler(struct clock_event_device *dev, int broadcast)
 {
 	dev->event_handler = tick_handle_periodic;
 }
+#else
+static void tick_handle_periodic(struct clock_event_device *dev) { }
+#endif
 #endif /* !BROADCAST */
 
 /* Functions related to oneshot broadcasting */


  reply	other threads:[~2015-03-31 22:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 18:39 Tyler Baker
2015-03-31 23:03 ` Rafael J. Wysocki [this message]
2015-03-31 23:27   ` Rafael J. Wysocki
2015-04-01  3:37     ` Tyler Baker
2015-04-01 21:46       ` Rafael J. Wysocki
2015-04-02  8:29         ` Peter Zijlstra
2015-04-02 22:09           ` Rafael J. Wysocki
2015-04-03  2:59           ` Tyler Baker
2015-04-03 11:07             ` Rafael J. Wysocki
2015-04-03 14:24               ` Peter Zijlstra
2015-04-07 17:08                 ` Tyler Baker

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=1489627.zlEOcOu4fx@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=john.stultz@linaro.org \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tyler.baker@linaro.org \
    /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®