On 02/25/2013 09:58 AM, Alessandro Zummo wrote: > On Sun, 24 Feb 2013 12:03:01 -0500 > Prarit Bhargava <pra...@redhat.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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
