Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266513AbUJFAg6 (ORCPT ); Tue, 5 Oct 2004 20:36:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266512AbUJFAg6 (ORCPT ); Tue, 5 Oct 2004 20:36:58 -0400 Received: from mx1.redhat.com ([66.187.233.31]:1753 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S266513AbUJFAfP (ORCPT ); Tue, 5 Oct 2004 20:35:15 -0400 Date: Tue, 5 Oct 2004 17:35:01 -0700 Message-Id: <200410060035.i960Z1Iv007864@magilla.sf.frob.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Christoph Lameter X-Fcc: ~/Mail/linus Cc: Linus Torvalds , Andrew Morton , Linux Kernel Mailing List , Ulrich Drepper , jbarnes@sgi.com Subject: Re: [PATCH] CPU time clock support in clock_* syscalls In-Reply-To: Christoph Lameter's message of Tuesday, 5 October 2004 14:28:18 -0700 X-Windows: garbage at your fingertips. Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 584 Lines: 15 > Maybe its best then to restrict this definition to glibc? I can't figure out what problem you think exists or what you are trying to gain here. > How will you provide the necessary hardware interface for the kernel > clocks? You again seem to be asking a question that makes no sense in the context that I have already explained. - 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/