mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Stanislav Fomichev <stfomichev@yandex-team.ru>,
	Thomas Gleixner <tglx@linutronix.de>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Stuart Hayes <stuart.w.hayes@gmail.com>,
	david.vrabel@citrix.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] hrtimers: add fast path to hrtimer_get_next_event
Date: Tue, 10 Jun 2014 09:42:42 +0200	[thread overview]
Message-ID: <20140610074242.GW3213@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKohpon3s3P2WE8oGiKgw8BU-3zGCPPjq=Bo9gAG4+7vVhTfdw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 338 bytes --]

On Mon, Jun 09, 2014 at 06:58:56PM +0530, Viresh Kumar wrote:
> 
> Even I was concerned about a bigger diff earlier and so didn't comment
> to rewrite it this way :)

WTF is wrong with you people? Who bloody cares how big diffs are? The
clarity of the resulting code is _far_ more important.

Please as to stop taking bong hits.

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-06-10  7:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09  9:23 [PATCH] hrtimers: conditionally lock/unlock spinlock in hrtimer_get_next_event Stanislav Fomichev
2014-06-09  9:27 ` Viresh Kumar
2014-06-09 11:06 ` Thomas Gleixner
2014-06-09 11:11   ` Stanislav Fomichev
2014-06-09 12:59     ` [PATCH v2] hrtimers: add fast path to hrtimer_get_next_event Stanislav Fomichev
2014-06-09 13:28       ` Viresh Kumar
2014-06-10  7:42         ` Peter Zijlstra [this message]
2014-06-09 14:44       ` Thomas Gleixner
2014-06-10  9:46         ` [PATCH v3] " Stanislav Fomichev

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=20140610074242.GW3213@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=david.vrabel@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=stfomichev@yandex-team.ru \
    --cc=stuart.w.hayes@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=viresh.kumar@linaro.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

Powered by JetHome