From: Avi Kivity <avi@qumranet.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Adrian Bunk <bunk@kernel.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Carsten Otte <cotte@de.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>,
kvm-devel@lists.sourceforge.net, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: s390 kvm_virtio.c build error
Date: Mon, 05 May 2008 16:00:52 +0300 [thread overview]
Message-ID: <481F0504.3010503@qumranet.com> (raw)
In-Reply-To: <200805051429.47446.borntraeger@de.ibm.com>
Christian Borntraeger wrote:
>> Hmm... this should help:
>>
>> ---
>> drivers/s390/kvm/kvm_virtio.c | 40
>>
> +++++++++++++++++++++++-----------------
>
>> 1 file changed, 23 insertions(+), 17 deletions(-)
>>
>
> Thanks Heiko.
> I did a short test and it seems to work.
>
> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
>
> This looks almost identical to Rusty's patch. Who is going to send this (or
> Rustys) patch to Linus?
>
I can, but tell me which one. Also, the patch (Heiko's) needs a
changelog entry and a signoff.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-05-05 13:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 17:47 s390 kvm_virtio.c build error Adrian Bunk
2008-05-03 17:47 ` Adrian Bunk
2008-05-03 17:47 ` Adrian Bunk
2008-05-04 19:25 ` Heiko Carstens
2008-05-04 19:25 ` Heiko Carstens
2008-05-05 12:29 ` Christian Borntraeger
2008-05-05 13:00 ` Avi Kivity [this message]
2008-05-05 13:06 ` Martin Schwidefsky
2008-05-05 13:20 ` Carsten Otte
2008-05-05 13:20 ` Carsten Otte
2008-05-06 14:39 ` Avi Kivity
2008-05-06 14:39 ` Avi Kivity
2008-05-14 10:37 ` Christian Borntraeger
2008-05-14 12:34 ` Avi Kivity
2008-05-05 0:19 ` Rusty Russell
2008-05-05 0:19 ` Rusty Russell
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=481F0504.3010503@qumranet.com \
--to=avi@qumranet.com \
--cc=borntraeger@de.ibm.com \
--cc=bunk@kernel.org \
--cc=cotte@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=schwidefsky@de.ibm.com \
/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.