[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <512F6EB0.1080706@redhat.com>
Date: Thu, 28 Feb 2013 09:50:24 -0500
From: Prarit Bhargava <prarit@...hat.com>
To: Alessandro Zummo <a.zummo@...ertech.it>
CC: John Stultz <john.stultz@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"x86@...nel.org" <x86@...nel.org>,
Matt Fleming <matt.fleming@...el.com>,
David Vrabel <david.vrabel@...rix.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Andi Kleen <ak@...ux.intel.com>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
"rtc-linux@...glegroups.com" <rtc-linux@...glegroups.com>
Subject: Re: [RFE PATCH 2/2] rtc, add write functionality to sysfs
On 02/25/2013 09:58 AM, Alessandro Zummo wrote:
> On Sun, 24 Feb 2013 12:03:01 -0500
> Prarit Bhargava <prarit@...hat.com> wrote:
>
>>
>> AFAICT there is no way for me to "test" or use the write from userspace.
>> hwclock uses the SET_TIME ioctl, which is a different code path AFAICT.
>>
>> I'd like to be at least able to test this stuff when we make changes to it so I
>> think having write functionality for date & time is worthwhile.
>>
>> For me, I'm using these to heavily test ntp and ntpdate over system reboots.
>
> the point is: who will benefit from this patch? users? distributions?
> embedded distributions? if it's useful, then just go for it.
This can be dropped IMO.
P.
>
>
>> OOC, Alessandro, why is the date & time split into two fields?
>
> because date and time are two different things and we expect
> sysfs to preferably have one value for each entry.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists