From: John Stultz <john.stultz@linaro.org>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, Matt Fleming <matt.fleming@intel.com>,
David Vrabel <david.vrabel@citrix.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <ak@linux.intel.com>,
linux-efi@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>
Subject: Re: [RFE PATCH 2/2] rtc, add write functionality to sysfs
Date: Fri, 22 Feb 2013 13:05:51 -0800 [thread overview]
Message-ID: <5127DDAF.2000403@linaro.org> (raw)
In-Reply-To: <5127DB2B.3030700@redhat.com>
On 02/22/2013 12:55 PM, Prarit Bhargava wrote:
>
> On 02/22/2013 03:43 PM, John Stultz wrote:
>> On 02/14/2013 09:02 AM, Prarit Bhargava wrote:
>>> /sys/class/rtc/rtcX/date and /sys/class/rtc/rtcX/time currently have
>>> read-only access. This patch introduces write functionality which will
>>> set the rtc time.
>>>
>>> Usage: echo YYYY-MM-DD > /sys/class/rtc/rtcX/date
>>> echo HH:MM:SS > /sys/class/rtc/rtcX/time
>> Why do we want to add a new interface here?
> John,
>
> I'm not adding a new interface. The current date/time interface only handles
> read and I'm introducing write.
>
Right, but what benefit does that provide?
(I'm not saying there isn't any, its just not clear from your patch why
this is a good thing.)
Also CC'ing Alessandro for his input.
thanks
-john
next prev parent reply other threads:[~2013-02-22 21:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 17:02 [RFE PATCH 0/2] x86, rtc, ntp, Enable full rtc synchronization Prarit Bhargava
2013-02-14 17:02 ` [RFE PATCH 1/2] x86, rtc, ntp, Do full rtc synchronization with ntp Prarit Bhargava
[not found] ` <1360861375-24131-2-git-send-email-prarit-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-02-22 20:42 ` John Stultz
[not found] ` <5127D853.6030703-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-02-24 17:12 ` Prarit Bhargava
[not found] ` <512A4A19.2090800-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-02-25 15:04 ` Alessandro Zummo
[not found] ` <1360861375-24131-1-git-send-email-prarit-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-02-14 17:02 ` [RFE PATCH 2/2] rtc, add write functionality to sysfs Prarit Bhargava
[not found] ` <1360861375-24131-3-git-send-email-prarit-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-02-22 20:43 ` John Stultz
[not found] ` <5127D884.6020701-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-02-22 20:55 ` Prarit Bhargava
2013-02-22 21:05 ` John Stultz [this message]
[not found] ` <5127DDAF.2000403-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-02-23 23:11 ` Alessandro Zummo
[not found] ` <B22B05C4-B8D2-44B9-971B-37913DE59EF6-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org>
2013-02-24 17:03 ` Prarit Bhargava
[not found] ` <512A47C5.3010500-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-02-25 14:58 ` Alessandro Zummo
[not found] ` <20130225155812.0758e093-7UIfgwKH8t5lecnr3/Sf3RLwuzhV/fVh@public.gmane.org>
2013-02-28 14:50 ` Prarit Bhargava
2013-02-28 18:51 ` 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=5127DDAF.2000403@linaro.org \
--to=john.stultz@linaro.org \
--cc=a.zummo@towertech.it \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=david.vrabel@citrix.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=prarit@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).