From: Greg KH <greg@kroah.com>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: stable@vger.kernel.org, kvm@vger.kernel.org,
Stephan Baerwolf <stephan.baerwolf@tu-ilmenau.de>,
Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [v3.0.y 1/2] KVM: x86: extend "struct x86_emulate_ops" with "get_cpuid"
Date: Fri, 23 Mar 2012 10:57:36 -0700 [thread overview]
Message-ID: <20120323175736.GA24754@kroah.com> (raw)
In-Reply-To: <4F6CB73A.1000502@canonical.com>
On Fri, Mar 23, 2012 at 06:47:38PM +0100, Stefan Bader wrote:
> On 23.03.2012 18:22, Greg KH wrote:
> > On Thu, Mar 22, 2012 at 09:50:43AM +0100, Stefan Bader wrote:
> >>> From eaee58e1433e1b16e686cfcdcbc207d4310a239f Mon Sep 17 00:00:00 2001
> >> From: =?UTF-8?q?Stephan=20B=C3=A4rwolf?=
> >> <stephan.baerwolf@tu-ilmenau.de> Date: Thu, 12 Jan 2012 16:43:03 +0100
> >> Subject: [PATCH 7/8] KVM: x86: extend "struct x86_emulate_ops" with
> >> "get_cpuid"
> >
> > Stefan, what's with the crappy header here? And the Subject? Ick.
> >
> > Come on, forcing me to hand-edit your patches just makes me grumpy...
> >
> > greg k-h
>
> Greg, this is exactly the patch you get by using git format-patch and send it
> away with git send-email. So I would say any grumpy or constructive comments
> should go to the git development mailing list. ;)
No it isn't at all. That's not how the patch looks using git-send-email
for anything I've ever sent out.
Don't blame the tool, use it correctly.
Hint, look at the 7/8 crap, what is that there for?
greg k-h
next prev parent reply other threads:[~2012-03-23 17:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 8:50 CVE-2012-0045 for 3.2.y, 3.0.y and 2.6.32.y (again) Stefan Bader
2012-03-22 8:50 ` [v2.6.32.y 1/2] KVM: x86: extend "struct x86_emulate_ops" with "get_cpuid" Stefan Bader
2012-03-22 8:50 ` [v2.6.32.y 2/2] KVM: x86: fix missing checks in syscall emulation Stefan Bader
2012-03-23 0:07 ` Marcelo Tosatti
2012-03-23 7:01 ` Stefan Bader
2012-03-22 8:50 ` [v3.0.y 1/2] KVM: x86: extend "struct x86_emulate_ops" with "get_cpuid" Stefan Bader
2012-03-23 14:00 ` Marcelo Tosatti
2012-03-23 17:22 ` Greg KH
2012-03-23 17:47 ` Stefan Bader
2012-03-23 17:57 ` Greg KH [this message]
2012-03-22 8:50 ` [v3.0.y 2/2] KVM: x86: fix missing checks in syscall emulation Stefan Bader
2012-03-23 14:01 ` Marcelo Tosatti
2012-03-22 8:50 ` [v3.2.y 1/2] KVM: x86: extend "struct x86_emulate_ops" with "get_cpuid" Stefan Bader
2012-03-22 8:50 ` [v3.2.y 2/2] KVM: x86: fix missing checks in syscall emulation Stefan Bader
2012-03-22 14:37 ` CVE-2012-0045 for 3.2.y, 3.0.y and 2.6.32.y (again) Greg KH
2012-03-23 1:47 ` Marcelo Tosatti
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=20120323175736.GA24754@kroah.com \
--to=greg@kroah.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stefan.bader@canonical.com \
--cc=stephan.baerwolf@tu-ilmenau.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 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.