From: Avi Kivity <avi@redhat.com>
To: "K.de Jong" <k.dejong@undifined.nl>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] These are my first patches to the kernel
Date: Sun, 13 Jun 2010 11:06:44 +0300 [thread overview]
Message-ID: <4C149194.2060507@redhat.com> (raw)
In-Reply-To: <AANLkTinUhfVvK7UOC6FiW9nG6xXRwCpDlAaedbSwFo7d@mail.gmail.com>
On 06/12/2010 03:17 PM, K.de Jong wrote:
> From 6b9ac8708d856a425a9aaa598acdea3d89485bde Mon Sep 17 00:00:00 2001
> From: UndiFineD<k.dejong@undifined.nl>
> Date: Sat, 12 Jun 2010 00:24:28 +0200
> Subject: [PATCH] These are my first patches to the kernel
> Janitor patches to kvm
> Linus2.6: virt/kvm/
>
>
Most of the patch is just whitespace changes, which don't improve the
code in any way. I much prefer patches that fix bugs or add features.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-06-13 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 12:17 [PATCH] These are my first patches to the kernel K.de Jong
2010-06-13 8:06 ` Avi Kivity [this message]
2010-06-13 12:56 ` K.de Jong
2010-06-13 13:33 ` Wolfram Sang
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=4C149194.2060507@redhat.com \
--to=avi@redhat.com \
--cc=k.dejong@undifined.nl \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).