From: Ingo Molnar <mingo@kernel.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [GIT PULL] Generic sched_clock fix for 3.11
Date: Mon, 19 Aug 2013 20:52:46 +0200 [thread overview]
Message-ID: <20130819185246.GA2994@gmail.com> (raw)
In-Reply-To: <20130819031306.GF3922@tarshish>
* Baruch Siach <baruch@tkos.co.il> wrote:
> Hi Ingo,
>
> On Mon, Aug 12, 2013 at 06:13:11PM +0200, Ingo Molnar wrote:
> >
> > * John Stultz <john.stultz@linaro.org> wrote:
> >
> > > Hey Thomas,
> > > Just one small fix against tip/timers/urgent for 3.11.
> > >
> > > thanks
> > > -john
> > >
> > >
> > > The following changes since commit b0ec636c93ddd77235bf0f023a8a95d78cb6cafe:
> > >
> > > Merge branch 'timers/clockevents' of
> > > git://git.linaro.org/people/dlezcano/clockevents into timers/urgent
> > > (2013-07-12 17:10:30 +0200)
> > >
> > > are available in the git repository at:
> > >
> > >
> > > git://git.linaro.org/people/jstultz/linux.git fortglx/3.11/time
> > >
> > > for you to fetch changes up to 53c035204253efe373d9ff166fae6147e8c693b6:
> > >
> > > sched_clock: Fix integer overflow (2013-07-22 16:24:22 -0700)
> > >
> > > ----------------------------------------------------------------
> > > Baruch Siach (1):
> > > sched_clock: Fix integer overflow
> > >
> > > kernel/time/sched_clock.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Pulled, thanks John!
>
> Do you intend to push it for -rc7?
Yes - Linus pulled it today, it should be in -rc7.
Thanks,
Ingo
prev parent reply other threads:[~2013-08-19 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 20:16 [GIT PULL] Generic sched_clock fix for 3.11 John Stultz
2013-08-12 16:13 ` Ingo Molnar
2013-08-19 3:13 ` Baruch Siach
2013-08-19 18:52 ` Ingo Molnar [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=20130819185246.GA2994@gmail.com \
--to=mingo@kernel.org \
--cc=baruch@tkos.co.il \
--cc=daniel.lezcano@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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