Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755838AbYABSep (ORCPT ); Wed, 2 Jan 2008 13:34:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752798AbYABSeg (ORCPT ); Wed, 2 Jan 2008 13:34:36 -0500 Received: from mx0.towertech.it ([213.215.222.73]:40459 "HELO mx0.towertech.it" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752444AbYABSef (ORCPT ); Wed, 2 Jan 2008 13:34:35 -0500 Date: Wed, 2 Jan 2008 19:34:15 +0100 From: Alessandro Zummo To: David Brownell Cc: stern@rowland.harvard.edu, rjw@sisk.pl, pavel@suse.cz, mingo@elte.hu, linux-pm@lists.linux-foundation.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, lenb@kernel.org, kay.sievers@vrfy.org, gregkh@suse.de, akpm@linux-foundation.org Subject: Re: [PATCH 0/4] PM: Do not destroy/create devices while suspended (rev. 2) Message-ID: <20080102193415.1d7af667@i1501.lan.towertech.it> In-Reply-To: <20080102181254.3469E28CE0F@adsl-69-226-248-13.dsl.pltn13.pacbell.net> References: <200801020032.45529.rjw@sisk.pl> <20080102105217.GA14731@elte.hu> <200801021356.59865.rjw@sisk.pl> <20080102131529.GA32160@elte.hu> <3ae72650801020655h6ec31ce8n5cd9014c00c9f6ad@mail.gmail.com> <20080102160137.GA21046@elte.hu> <20080102175400.3C2E0EF588@adsl-69-226-248-13.dsl.pltn13.pacbell.net> <20080102190537.2fc735fe@i1501.lan.towertech.it> <20080102181254.3469E28CE0F@adsl-69-226-248-13.dsl.pltn13.pacbell.net> Organization: Tower Technologies X-Mailer: Sylpheed 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: 998 Lines: 29 On Wed, 02 Jan 2008 10:12:54 -0800 David Brownell wrote: > > > It'd need to have some NTP sync solution for RTC_LIB devices, but > > > ISTR the gentime stuff still assumes an update_persistent_clock() > > > that doesn't sleep ... and hence can't be used with I2C based RTCs. > > > > I still believe NTP sync stuff should be done outside of the kernel. > > given the mean accuracy of RTC chips and other sync factors, imho > > you haven't so much to gain with an in-kernel sync code. > > Then the kernel/time/ntp.c stuff should be removed on all systems? I'd say yes, but I think that would be dangerous to my own life :) -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it -- 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/