mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Pavel Tatashin <pasha.tatashin@oracle.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com,
	peterz@infradead.org, hpa@zytor.com
Subject: Re: [v2 0/9] Early boot time stamps for x86
Date: Sat, 25 Mar 2017 11:25:46 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1703251119180.5612@nanos> (raw)
In-Reply-To: <1490368899-877997-1-git-send-email-pasha.tatashin@oracle.com>

On Fri, 24 Mar 2017, Pavel Tatashin wrote:

> changelog
> ---------
> v1 - v2
> 	In patch "x86/tsc: tsc early":
> 	- added tsc_adjusted_early()
> 	- fixed 32-bit compile error use do_div()

Did you actually read my last reply on V1 of this?

I made it entirely clear that the way this is done, i.e. hacking it into
the earliest boost stage is not going to happen.

Further I asked you to hold off until I found some time to look into this
in detail.

So what's the point of ignoring what I said and resending the whole lot
with some more hackery applied?

I don't care about you wasting your time, but I very much care about my
time.

Thanks,

	tglx

  parent reply	other threads:[~2017-03-25 10:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24 15:21 Pavel Tatashin
2017-03-24 15:21 ` [v2 1/9] sched/clock: broken stable to unstable transfer Pavel Tatashin
2017-03-24 15:21 ` [v2 2/9] sched/clock: interface to allow timestamps early in boot Pavel Tatashin
2017-03-24 15:21 ` [v2 3/9] x86/cpu: determining x86 vendor early Pavel Tatashin
2017-03-24 15:21 ` [v2 4/9] x86/tsc: early MSR-based CPU/TSC frequency discovery Pavel Tatashin
2017-03-24 15:21 ` [v2 5/9] x86/tsc: disable early messages from quick_pit_calibrate Pavel Tatashin
2017-03-24 15:21 ` [v2 6/9] x86/tsc: use cpuid to determine TSC frequency Pavel Tatashin
2017-03-24 15:21 ` [v2 7/9] x86/tsc: use cpuid to determine CPU frequency Pavel Tatashin
2017-03-24 15:21 ` [v2 8/9] x86/tsc: tsc early Pavel Tatashin
2017-03-24 15:21 ` [v2 9/9] x86/tsc: use " Pavel Tatashin
2017-03-28  1:08   ` [lkp-robot] [x86/tsc] 07e7eaa3bc: BUG:kernel_reboot-without-warning_in_early-boot_stage kernel test robot
2017-03-25 10:25 ` Thomas Gleixner [this message]
2017-03-25 13:55   ` [v2 0/9] Early boot time stamps for x86 Pasha Tatashin
2017-03-25 18:36     ` Thomas Gleixner
2017-03-25 19:45       ` Pasha Tatashin

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=alpine.DEB.2.20.1703251119180.5612@nanos \
    --to=tglx@linutronix.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pasha.tatashin@oracle.com \
    --cc=peterz@infradead.org \
    --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®