mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] timekeeping: Fix build when generic clockevents are enabled
Date: Thu, 9 Aug 2012 21:43:03 +0200	[thread overview]
Message-ID: <201208092143.03871.rjw@sisk.pl> (raw)
In-Reply-To: <1344513580-9571-1-git-send-email-broonie@opensource.wolfsonmicro.com>

On Thursday, August 09, 2012, Mark Brown wrote:
> Commit a2c204 (timekeeping: Add suspend and resume of clock event devices)
> added suspend and resume operations for clockevents but did not provide
> stubs for these functions, breaking the build when clockevents are not
> being built. Add the stubs.
> 
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>

I've fixed that already in my tree.

Thanks,
Rafael


> ---
>  include/linux/clockchips.h |    2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/include/linux/clockchips.h b/include/linux/clockchips.h
> index ca060db..4f9c280 100644
> --- a/include/linux/clockchips.h
> +++ b/include/linux/clockchips.h
> @@ -170,6 +170,8 @@ extern void clockevents_notify(unsigned long reason, void *arg);
>  #else /* CONFIG_GENERIC_CLOCKEVENTS_BUILD */
>  
>  #define clockevents_notify(reason, arg) do { } while (0)
> +#define clockevents_suspend() do { } while (0)
> +#define clockevents_resume() do { } while (0)
>  
>  #endif
>  
> 


  reply	other threads:[~2012-08-09 19:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 11:59 Mark Brown
2012-08-09 19:43 ` Rafael J. Wysocki [this message]
2012-08-09 19:48 ` Rafael J. Wysocki
2012-08-13 15:07 ` Thomas Gleixner
2012-08-13 15:07   ` Mark Brown
2012-08-13 18:48     ` Rafael J. Wysocki

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=201208092143.03871.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.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

Powered by JetHome