From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Gleb Natapov <gleb@kernel.org>, KVM list <kvm@vger.kernel.org>
Subject: Re: [GIT PULL] KVM changes for 3.17-rc4
Date: Fri, 05 Sep 2014 23:09:18 +0200 [thread overview]
Message-ID: <540A267E.1070002@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1409052254450.5472@nanos>
Il 05/09/2014 22:58, Thomas Gleixner ha scritto:
> Nothing new there. Forgot to push out, or perhaps to use "-f" to
> overwrite the previous tag of the same name?
It's there now. Probably a --dry-run too much (I have
push=+refs/tags/for-linus:refs/tags/for-linus in the remote configuration).
> And even if there would be something, please do not pull the top most
> commit b11ba8c62be3eb (KVM: x86: fix kvmclock breakage from timers
> branch merge).
>
> That one is blantanly wrong and just hacks badly around a brown
> paperbag bug in the core timekeeping code, which I introduced in the
> last overhaul.
It's not wrong, it's just different. The commit message says clearly
that besides acting as a workaround, I find the patched code easier to
understand, and I clearly stated the same in the tag message.
Paolo
next prev parent reply other threads:[~2014-09-05 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 10:16 [GIT PULL] KVM changes for 3.17-rc4 Paolo Bonzini
2014-09-05 20:44 ` Linus Torvalds
2014-09-05 20:58 ` Thomas Gleixner
2014-09-05 21:09 ` Paolo Bonzini [this message]
2014-09-05 21:24 ` Thomas Gleixner
2014-09-05 21:45 ` Paolo Bonzini
2014-09-05 22:43 ` Thomas Gleixner
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=540A267E.1070002@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.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