public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Sameer Nanda <snanda@chromium.org>
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
Date: Thu, 7 Oct 2010 11:15:36 -0700	[thread overview]
Message-ID: <20101007181536.GA24811@suse.de> (raw)
In-Reply-To: <AANLkTik=imw5XRpXSkboyB6txXio6Y65bLV+EdfvRXg3@mail.gmail.com>

On Thu, Oct 07, 2010 at 11:05:21AM -0700, Sameer Nanda wrote:
> On Thu, Oct 7, 2010 at 10:46 AM, Greg KH <gregkh@suse.de> wrote:
> > On Thu, Oct 07, 2010 at 10:43:34AM -0700, Sameer Nanda wrote:
> >> On Wed, Oct 6, 2010 at 7:19 PM, Greg KH <gregkh@suse.de> 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?
> 
> Aside from complaining to the BIOS vendors, no :)

Then I would not recommend adding this patch, as it is irrelevant for
99.9999% of all Linux users.

thanks,

greg k-h

  reply	other threads:[~2010-10-07 18:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 23:15 [PATCH] ACPI: Read TSC upon resume Sameer Nanda
2010-10-07  2:19 ` Greg KH
     [not found]   ` <AANLkTimE2h46iZkj_amvgUg5UwN9xjuwqdW5TB+XccYy@mail.gmail.com>
2010-10-07 17:46     ` Greg KH
2010-10-07 18:05       ` Sameer Nanda
2010-10-07 18:15         ` Greg KH [this message]
2010-10-07 21:44           ` Rafael J. Wysocki
2010-10-16  3:03             ` Koornstra, Reinoud
2010-10-18  2:41               ` Chen Gong
2010-10-07 17:58   ` Sameer Nanda
2010-10-07 19:59     ` Rafael J. Wysocki
2010-10-07 21:27       ` Sameer Nanda
2010-10-07 21:43         ` Rafael J. Wysocki

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=20101007181536.GA24811@suse.de \
    --to=gregkh@suse.de \
    --cc=apw@canonical.com \
    --cc=brad.figg@canonical.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snanda@chromium.org \
    --cc=stefan.bader@canonical.com \
    /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