From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753872Ab0JGR4Q (ORCPT ); Thu, 7 Oct 2010 13:56:16 -0400 Received: from cantor.suse.de ([195.135.220.2]:49307 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751071Ab0JGR4N (ORCPT ); Thu, 7 Oct 2010 13:56:13 -0400 Date: Thu, 7 Oct 2010 10:46:26 -0700 From: Greg KH To: Sameer Nanda Cc: lenb@kernel.org, stefan.bader@canonical.com, brad.figg@canonical.com, apw@canonical.com, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] ACPI: Read TSC upon resume Message-ID: <20101007174626.GA31541@suse.de> References: <1286406919-6236-1-git-send-email-snanda@chromium.org> <20101007021959.GA7300@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 07, 2010 at 10:43:34AM -0700, Sameer Nanda wrote: > On Wed, Oct 6, 2010 at 7:19 PM, Greg KH wrote: > > And are you always going to be printing this out? Why do we want to > > know this every time? > > > > Yes, every time. This helps track variance in BIOS resume times within a > single boot. Is that really something that users can do something about? I can understand when you are trying to work with a BIOS company, but otherwise, this seems quite pointless. thanks, greg k-h