From: Ingo Molnar <mingo@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Fr??d??ric Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] timers/nohz changes for v3.12
Date: Tue, 3 Sep 2013 20:20:52 +0200 [thread overview]
Message-ID: <20130903182052.GA30757@gmail.com> (raw)
In-Reply-To: <CAMuHMdWPE7OxWFNENe7qAx4+2rhMwbK6kG4LzXCxKMMKsxKM2w@mail.gmail.com>
* Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Tue, Sep 3, 2013 at 4:13 PM, Ingo Molnar <mingo@kernel.org> wrote:
> > Please pull the latest timers-nohz-for-linus git tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-nohz-for-linus
> >
> > HEAD: c2e7fcf53c3cb02b4ada1c66a9bc8a4d97d58aba nohz: Include local CPU in full dynticks global kick
> >
> > It mostly contains fixes and full dynticks off-case optimizations,
> > by Frederic Weisbecker.
> >
> > NOTE: for some reason my pull request scripts failed to generate a proper
> > diffstat so I've generated the shortlog and diffstat manually. All
> > resulting mistakes are mine.
>
> You forgot to push timers-nohz-for-linus, or it hadn't propagated from
> ra.kernel.org to git.kernel.org?
Hm, it's visible here.
> git (1.7.9.5, Ubuntu 12.04LTS) doesn't seem to complain about missing or
> stale branches on the remote, and just does something it thinks is
> right.
My scripts check that the remote branch is visible and is the same as the
local branch - but I guess there's a way that check can go wrong as well.
Thanks,
Ingo
prev parent reply other threads:[~2013-09-03 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 14:13 [GIT PULL] timers/nohz changes for v3.12 Ingo Molnar
2013-09-03 16:34 ` Geert Uytterhoeven
2013-09-03 18:20 ` 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=20130903182052.GA30757@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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