From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Oleg Nesterov <oleg@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: [GIT PULL] dynticks updates for 3.13
Date: Mon, 2 Dec 2013 15:39:34 +0100 [thread overview]
Message-ID: <20131202143927.GB6758@localhost.localdomain> (raw)
In-Reply-To: <20131130141106.GA19997@gmail.com>
On Sat, Nov 30, 2013 at 03:11:06PM +0100, Ingo Molnar wrote:
>
> * Ingo Molnar <mingo@kernel.org> wrote:
>
> >
> > * Frederic Weisbecker <fweisbec@gmail.com> wrote:
> >
> > > Ingo,
> > >
> > > Please pull the timers/core branch that can be found at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> > > timers/core
> > >
> > > It passed through 0-day testing. I'm proposing it for 3.13 just in case but I'm ok
> > > as well if you think it's too late and should be delayed for 3.14
> >
> > Pulled into tip:timers/core, thanks Frederic!
>
> Hm, I had to unpull it due to build failure:
>
> kernel/time/tick-sched.c:1054:2: error: too few arguments to function ‘tick_check_nohz’
Aie! I realize now that Wu Fengguang's 0-day testing reported me this on the 1st version
of this patchset. Then I got distracted with other things and forgot to fix it. And it didn't
warn me on the 2nd take to avoid spamming me.
Anyway, I'll fix this and resend.
>
> I guess this means that it's better to rebase this series - at which
> point the other complaints I had could be addressed as well?
Yeah sure.
Thanks!
>
> Thanks,
>
> Ingo
next prev parent reply other threads:[~2013-12-02 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 14:49 [GIT PULL] dynticks updates for 3.13 Frederic Weisbecker
2013-11-30 13:59 ` Ingo Molnar
2013-11-30 14:11 ` Ingo Molnar
2013-12-02 14:39 ` Frederic Weisbecker [this message]
2013-12-02 14:48 ` Frederic Weisbecker
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=20131202143927.GB6758@localhost.localdomain \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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