mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jiri Kosina <jkosina@suse.cz>,
	x86@kernel.org, Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] time: x86: report_lost_ticks doesn't exist any more
Date: Wed, 23 Jan 2013 08:43:45 -0600	[thread overview]
Message-ID: <4b47e67f-b4b2-48ed-82cb-4ddaca5e1e77@email.android.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1301231212420.20374@pobox.suse.cz>

That works.  You can add my Ack if you want.  Thanks!

Jiri Kosina <jkosina@suse.cz> wrote:

>On Thu, 17 Jan 2013, Jiri Kosina wrote:
>
>> 'report_lost_ticks' parameter has been removed back in 2007 through 
>> 1489939f0ab ("time: x86_64: convert x86_64 to use GENERIC_TIME").
>> 
>> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
>> ---
>>  Documentation/x86/x86_64/boot-options.txt |    4 ----
>>  1 files changed, 0 insertions(+), 4 deletions(-)
>> 
>> diff --git a/Documentation/x86/x86_64/boot-options.txt
>b/Documentation/x86/x86_64/boot-options.txt
>> index de38429..e015a83 100644
>> --- a/Documentation/x86/x86_64/boot-options.txt
>> +++ b/Documentation/x86/x86_64/boot-options.txt
>> @@ -112,10 +112,6 @@ Timing
>>    This can be used to work around timing problems on multiprocessor
>systems
>>    with not properly synchronized CPUs.
>>  
>> -  report_lost_ticks
>> -  Report when timer interrupts are lost because some code turned off
>> -  interrupts for too long.
>> -
>>    nohpet
>>    Don't use the HPET timer.
>
>Noone seems to have picked this up, I am taking it through trivial.git

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.

      reply	other threads:[~2013-01-23 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 10:21 Jiri Kosina
2013-01-23 11:12 ` Jiri Kosina
2013-01-23 14:43   ` H. Peter Anvin [this message]

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=4b47e67f-b4b2-48ed-82cb-4ddaca5e1e77@email.android.com \
    --to=hpa@zytor.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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

all inboxes | Powered by JetHome®