From: Avi Kivity <avi@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: KVM list <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] KVM fix for 3.1-rc5
Date: Wed, 07 Sep 2011 07:06:20 +0300 [thread overview]
Message-ID: <4E66EDBC.4040102@redhat.com> (raw)
In-Reply-To: <CA+55aFw+EJr9FhZZnj0re8hyH5+gFesDso2mX+PWck31ivnWYQ@mail.gmail.com>
On 09/07/2011 02:20 AM, Linus Torvalds wrote:
> On Mon, Sep 5, 2011 at 2:42 AM, Avi Kivity<avi@redhat.com> wrote:
> > Linus, please pull from
> >
> > git://github.com/avikivity/kvm.git kvm-updates/3.1
> >
> > to receive a fix for a build failure due to a missing instruction size
> > suffix in inline assembly.
>
> Again, please give me a warm and fuzzy feeling that this is really
> Avi, and the right thing to do, rather than just a "please pull from
> this random tree".
Yup, it's the genuine thing here, and the s/mul/mulq/ is not an
incredibly clever backdoor.
> It's not that I don't think you are you, but I want people to actually
> *think* about what they are doing and sending me. When you give me a
> kernel.org address, I know you have access to kernel.org, and that
> makes me believe you are you. When you give me a github address, that
> doesn't really mean anything.
>
>
Well, these days access to kernel.org proves a lot less than it used to,
unfortunately.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-09-07 4:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 9:42 [GIT PULL] KVM fix for 3.1-rc5 Avi Kivity
2011-09-06 23:20 ` Linus Torvalds
2011-09-07 1:19 ` Josh Boyer
2011-09-07 1:37 ` Linus Torvalds
2011-09-07 4:06 ` Avi Kivity [this message]
2011-09-13 1:37 ` Arnaud Lacombe
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=4E66EDBC.4040102@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.