public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <johnstul@us.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	David Daney <ddaney.cavm@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>, Chen Jie <chenj@lemote.com>,
	zhangfx <zhangfx@lemote.com>
Subject: Re: [GIT PULL] clocksource:  Avoid possible mult overflows
Date: Fri, 11 Nov 2011 11:04:09 -0800	[thread overview]
Message-ID: <1321038249.2129.4.camel@js-netbook> (raw)
In-Reply-To: <20111111071225.GB14347@elte.hu>

On Fri, 2011-11-11 at 08:12 +0100, Ingo Molnar wrote:
> * john stultz <johnstul@us.ibm.com> wrote:
> 
> > Hey Ingo,
> > 	Here's the revised fix to the mult overflow issue against
> > tip/timers/core. Let me know if you hit any other issues.
> > 
> > thanks
> > -john
> > 
> > 
> >   git://git.linaro.org/people/jstultz/linux.git formingo/3.2/tip/timers/core
> 
> Pulled, thanks John!
> 
> Note, it was not based on the latest tip:timers/core branch of:
> 
>     git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git

Ah. I had set my remote to:
	git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git

> and it conflicted with another patch of yours (trivially). I've 
> resolved the conflict, please double check that it's all fine.

So, tip/timers/core doesn't seem to have the patch.

tip/timers/urgent has the original version, not the current v3.

Where exactly did you pull this one to?

thanks
-john


      reply	other threads:[~2011-11-11 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-10 19:33 [GIT PULL] clocksource: Avoid possible mult overflows john stultz
2011-11-11  7:12 ` Ingo Molnar
2011-11-11 19:04   ` John Stultz [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=1321038249.2129.4.camel@js-netbook \
    --to=johnstul@us.ibm.com \
    --cc=chenj@lemote.com \
    --cc=ddaney.cavm@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=zhangfx@lemote.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