From: Andrew Morton <akpm@linux-foundation.org>
To: David Fries <david@fries.net>
Cc: linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
"Matthew Garrett" <mjg@redhat.com>,
"Alessandro Zummo" <a.zummo@towertech.it>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH] rtc_sysfs_show_hctosys 0 if resume failed
Date: Fri, 7 Sep 2012 16:56:26 -0700 [thread overview]
Message-ID: <20120907165626.c9b842b1.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120826021931.GA20620@spacedout.fries.net>
On Sat, 25 Aug 2012 21:19:31 -0500
David Fries <david@fries.net> wrote:
> Subject: [PATCH] rtc_sysfs_show_hctosys 0 if resume failed
This doesn't make much sense. Did you mean "rtc_sysfs_show_hctosys():
display 0 if resume failed"?
> The original rtc_sysfs_show_hctosys returnd 1 if this device was the
> CONFIG_RTC_HCTOSYS_DEVICE device, a later patch checked
> rtc_hctosys_ret from boot, this verifies boot do_settimeofday
> succeeded, and sets rtc_hctosys_ret in resume to indicate when
> adjusting the clock from resume fails.
>
> This uses only CONFIG_RTC_HCTOSYS_DEVICE for conditional compilation
> instead of it and CONFIG_RTC_HCTOSYS. rtc_hctosys_ret was moved to
> class.c so rtc_hctosys can be removed with just a Kconfig change if
> boot time setting isn't desired.
And this makes my head spin. What does the patch actually do? I think
it might fix a bug, but it's unclear what that bug is.
Can you please write a better changelog and title and resend?
Sorry.
next prev parent reply other threads:[~2012-09-07 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-26 2:19 David Fries
2012-09-07 23:56 ` Andrew Morton [this message]
2012-09-08 1:26 ` [PATCH] rtc_sysfs_show_hctosys(): display " David Fries
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=20120907165626.c9b842b1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.zummo@towertech.it \
--cc=david@fries.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=rtc-linux@googlegroups.com \
--cc=u.kleine-koenig@pengutronix.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