From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Kyle Moffett <kyle@moffetthome.net>,
Thomas Gleixner <tglx@linutronix.de>,
Alexander Shishkin <virtuoso@slind.org>,
Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
John Stultz <johnstul@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Kay Sievers <kay.sievers@vrfy.org>, Greg KH <gregkh@suse.de>,
Chris Friesen <chris.friesen@genband.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [PATCHv6 0/7] system time changes notification
Date: Fri, 12 Nov 2010 11:25:09 +0000 [thread overview]
Message-ID: <20101112112509.5948219a@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20101112105358.GA20425@riccoc20.at.omicron.at>
> Did you see my recent post on dynamic clock ids, from Nov 4th?
> It implements the clock lifetime cycle, and I would like to here your
> comments on that.
Its hard to see the intended API from the patches, but I remain strongly
convinced that you must be able to open/close and use normal file
operations on a clock.
Having the id space nibble away at the future cpu clock range and pid
size is always a bit iffy.
The rest of the stuff - kref counting and the like look nice and it's
definitely going the right way about that.
Alan
next prev parent reply other threads:[~2010-11-12 11:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 19:29 Alexander Shishkin
2010-11-11 19:29 ` [PATCHv6 1/7] notify userspace about time changes Alexander Shishkin
2010-11-11 20:55 ` Arnd Bergmann
2010-11-11 19:29 ` [PATCHv6 2/7] wire up sys_time_change_notify() on ARM Alexander Shishkin
2010-11-11 19:29 ` [PATCHv6 3/7] wire up sys_time_change_notify() on x86 Alexander Shishkin
2010-11-11 19:29 ` [PATCHv6 4/7] wire up sys_time_change_notify() on ia64 Alexander Shishkin
2010-11-11 19:30 ` [PATCHv6 5/7] wire up sys_time_change_notify() on s390 Alexander Shishkin
2010-11-11 19:30 ` [PATCHv6 6/7] wire up sys_time_change_notify() on powerpc Alexander Shishkin
2010-11-11 19:30 ` [PATCHv6 7/7] wire up sys_time_change_notify() on blackfin Alexander Shishkin
2010-11-11 20:28 ` [PATCHv6 0/7] system time changes notification Valdis.Kletnieks
2010-11-11 20:51 ` Alexander Shishkin
2010-11-11 21:16 ` Thomas Gleixner
2010-11-11 22:11 ` Kyle Moffett
2010-11-11 22:36 ` john stultz
2010-11-11 23:19 ` Kyle Moffett
2010-11-11 23:41 ` john stultz
2010-11-11 23:45 ` john stultz
2010-11-11 22:50 ` Thomas Gleixner
2010-11-12 2:35 ` Davide Libenzi
2010-11-17 19:06 ` Alexander Shishkin
2010-11-17 20:42 ` Davide Libenzi
2010-11-17 21:29 ` Alexander Shishkin
2010-11-17 21:34 ` Kay Sievers
2010-11-18 15:59 ` Alexander Shishkin
2010-11-17 21:46 ` Thomas Gleixner
2010-11-18 9:49 ` Alexander Shishkin
2010-11-18 13:08 ` Artem Bityutskiy
2010-11-12 9:25 ` Alan Cox
2010-11-12 10:53 ` Richard Cochran
2010-11-12 11:25 ` Alan Cox [this message]
2010-11-12 10:47 ` Kay Sievers
2010-11-12 12:30 ` Alexander Shishkin
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=20101112112509.5948219a@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=chris.friesen@genband.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=johnstul@us.ibm.com \
--cc=kay.sievers@vrfy.org \
--cc=kirill@shutemov.name \
--cc=kyle@moffetthome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=virtuoso@slind.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
all inboxes | Powered by JetHome®