public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: Feng Tang <feng.tang@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Alessandro Zummo <a.zummo@towertech.it>,
	linux-kernel@vger.kernel.org,
	Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Subject: Re: [PATCH v2 3/3] timekeeping: Add CONFIG_HAS_PERSISTENT_CLOCK option
Date: Tue, 15 Jan 2013 11:50:18 -0800	[thread overview]
Message-ID: <50F5B2FA.6030006@linaro.org> (raw)
In-Reply-To: <1358266189-8812-3-git-send-email-feng.tang@intel.com>

On 01/15/2013 08:09 AM, Feng Tang wrote:
> Make the persistent clock check a kernel config option, so that some
> platform can explicitely select it, also make CONFIG_RTC_HCTOSYS depends
> on its non-existence, which could prevent the persistent clock and RTC
> code from doing similar thing twice during system's init/suspend/resume
> phases.
>
> If the CONFIG_HAS_PERSISTENT_CLOCK=n, then no change happens for kernel
> which still does the persistent clock check in timekeeping_init().
>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Suggested-by: John Stultz <john.stultz@linaro.org>
> Signed-off-by: Feng Tang <feng.tang@intel.com>

Applied. I also added a dependency for Jason's CONFIG_RTC_SYSTOHC.

thanks
-john


  reply	other threads:[~2013-01-15 19:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 16:09 [PATCH v2 1/3] timekeeping: Add persistent_clock_exist flag Feng Tang
2013-01-15 16:09 ` [PATCH v2 2/3] rtc: Skip the suspend/resume handling if persistent clock exist Feng Tang
2013-01-15 19:49   ` John Stultz
2013-01-15 16:09 ` [PATCH v2 3/3] timekeeping: Add CONFIG_HAS_PERSISTENT_CLOCK option Feng Tang
2013-01-15 19:50   ` John Stultz [this message]
2013-01-22 19:44     ` Jason Gunthorpe
2013-01-22 19:49       ` John Stultz
2013-01-26  1:07         ` John Stultz
2013-01-15 19:48 ` [PATCH v2 1/3] timekeeping: Add persistent_clock_exist flag John Stultz

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=50F5B2FA.6030006@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=a.zummo@towertech.it \
    --cc=feng.tang@intel.com \
    --cc=jgunthorpe@obsidianresearch.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