From: Feng Tang <feng.tang@intel.com>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>, Kay Sievers <kay@vrfy.org>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] time: Revert ALWAYS_USE_PERSISTENT_CLOCK compile time optimizaitons
Date: Thu, 25 Apr 2013 14:30:45 +0800 [thread overview]
Message-ID: <20130425063045.GA2597@feng-snb> (raw)
In-Reply-To: <1366828376-18124-1-git-send-email-john.stultz@linaro.org>
On Wed, Apr 24, 2013 at 11:32:56AM -0700, John Stultz wrote:
> Kay Sievers noted that the ALWAYS_USE_PERSISTENT_CLOCK config,
> which enables some minor compile time optimization to avoid
> uncessary code in mostly the suspend/resume path could cause
> problems for userland.
>
> In particular, the dependency for RTC_HCTOSYS on
> !ALWAYS_USE_PERSISTENT_CLOCK, which avoids setting the time
> twice and simplifies suspend/resume, has the side effect
> of causing the /sys/class/rtc/rtcN/hctosys flag to always be
> zero, and this flag is commonly used by udev to setup the
> /dev/rtc symlink to /dev/rtcN, which can cause pain for
> older applications.
>
> While the udev rules could use some work to be less fragile,
> breaking userland should strongly be avoided. Additionally
> the compile time optimizations are fairly minor, and the code
> being optimized is likely to be reworked in the future, so
> lets revert this change.
>
> I suspect this will miss 3.9-final, so marking it for 3.9-stable.
thanks
Acked-by: Feng Tang <feng.tang@intel.com>
prev parent reply other threads:[~2013-04-25 6:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 18:32 [PATCH] time: Revert ALWAYS_USE_PERSISTENT_CLOCK compile time optimizaitons John Stultz
2013-04-24 18:41 ` Kay Sievers
2013-04-24 18:55 ` John Stultz
2013-04-24 19:18 ` Kay Sievers
2013-04-24 21:24 ` John Stultz
2013-04-25 23:22 ` Kay Sievers
2013-04-24 19:44 ` Kay Sievers
2013-04-24 21:26 ` John Stultz
2013-04-25 6:30 ` Feng Tang [this message]
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=20130425063045.GA2597@feng-snb \
--to=feng.tang@intel.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=john.stultz@linaro.org \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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