Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757453Ab0KLL1O (ORCPT ); Fri, 12 Nov 2010 06:27:14 -0500 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:52745 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756612Ab0KLL1N (ORCPT ); Fri, 12 Nov 2010 06:27:13 -0500 Date: Fri, 12 Nov 2010 11:25:09 +0000 From: Alan Cox To: Richard Cochran Cc: Kyle Moffett , Thomas Gleixner , Alexander Shishkin , Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org, John Stultz , Andrew Morton , "H. Peter Anvin" , Kay Sievers , Greg KH , Chris Friesen , Linus Torvalds , "Kirill A. Shutemov" Subject: Re: [PATCHv6 0/7] system time changes notification Message-ID: <20101112112509.5948219a@lxorguk.ukuu.org.uk> In-Reply-To: <20101112105358.GA20425@riccoc20.at.omicron.at> References: <1289503802-22444-1-git-send-email-virtuoso@slind.org> <22542.1289507293@localhost> <20101111205123.GC10585@shisha.kicks-ass.net> <20101112092504.6b8db05b@lxorguk.ukuu.org.uk> <20101112105358.GA20425@riccoc20.at.omicron.at> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.18.9; x86_64-redhat-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 783 Lines: 20 > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/