- Subject: Re: [PATCH V9 08/13] posix clocks: cleanup the CLOCK_DISPTACH macro
- From: Richard Cochran <richardcochran@xxxxxxxxx>
- Date: Sat, 22 Jan 2011 13:38:40 +0100
- Cc: linux-kernel@xxxxxxxxxxxxxxx, linux-api@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxxxxxx, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, Arnd Bergmann <arnd@xxxxxxxx>, Christoph Lameter <cl@xxxxxxxxx>, David Miller <davem@xxxxxxxxxxxxx>, John Stultz <johnstul@xxxxxxxxxx>, Krzysztof Halasa <khc@xxxxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, Rodolfo Giometti <giometti@xxxxxxxx>
- In-reply-to: <alpine.LFD.2.00.1101131745400.2678@xxxxxxxxxxxxxxxxxxxxxxx>
- References: <cover.1294917347.git.richard.cochran@xxxxxxxxxx> <90b2beef441615d01c93fcad029c44af4e505c5f.1294917348.git.richard.cochran@xxxxxxxxxx> <alpine.LFD.2.00.1101131745400.2678@xxxxxxxxxxxxxxxxxxxxxxx>
- User-agent: Mutt/1.5.20 (2009-06-14)
On Thu, Jan 13, 2011 at 06:03:24PM +0100, Thomas Gleixner wrote:
> On Thu, 13 Jan 2011, Richard Cochran wrote:
> > int posix_cpu_clock_getres(const clockid_t which_clock, struct timespec *ts);
> > int posix_cpu_clock_get(const clockid_t which_clock, struct timespec *ts);
> > -int posix_cpu_clock_set(const clockid_t which_clock, const struct timespec *ts);
> > +int posix_cpu_clock_set(const clockid_t which_clock, struct timespec *ts);
>
> Shouldn't we change the clock_set function to have *ts const in all places ?
The common_clock_set function calls:
do_sys_settimeofday
security_settime
cap_settime
do_settimeofday
so all their signatures must also change.
Should I add that into my patch set?
Thanks,
Richard
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Home]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Free Online Dating]
[Linux Kernel]
[Linux SCSI]
[XFree86]