public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@6wind.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, Olivier Matz <olivier.matz@6wind.com>,
	kvm@vger.kernel.org, claudio.fontana@huawei.com,
	armbru@redhat.com, pbonzini@redhat.com, jani.kokkonen@huawei.com,
	cam@cs.ualberta.ca
Subject: Re: [Qemu-devel] [PATCH v3 1/2] contrib: add ivshmem client and server
Date: Mon, 18 Aug 2014 14:09:42 +0200	[thread overview]
Message-ID: <53F1ED06.9020408@6wind.com> (raw)
In-Reply-To: <20140808145132.GC13382@stefanha-thinkpad.redhat.com>


On 08/08/2014 04:51 PM, Stefan Hajnoczi wrote:
> On Fri, Aug 08, 2014 at 10:55:17AM +0200, David Marchand wrote:
>
> Looks good, a few minor comments:
>
>> diff --git a/contrib/ivshmem-client/Makefile b/contrib/ivshmem-client/Makefile
>> new file mode 100644
>> index 0000000..eee97c6
>> --- /dev/null
>> +++ b/contrib/ivshmem-client/Makefile
>> @@ -0,0 +1,29 @@
>
> CCed Peter Maydell for a second opinion, I'd suggest hooking up to
> QEMU's top-level ./Makefile.  QEMU does not do recursive make.
>
> The advantages of hooking up QEMU's Makefile are:
>
> 1. So that ivshmem client/server code is built by default (on supported
>     host platforms) and bitrot is avoided.
>
> 2. So that you don't have to duplicate rules.mak or any other build
>     infrastructure.
>

Ok, done.
But in this case, should we really keep the files in contrib/ ?
I used this directory but I am not too sure about this.

Maybe hw/misc/ivshmem/ would be better ?


The rest of your comments have been integrated in my tree.

Is it preferred to send fixes aside the original patches ? or should I 
send a squashed version ?
(I suppose the former is better as it is easier to read).


Thanks Stefan.


-- 
David Marchand

  reply	other threads:[~2014-08-18 12:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08  8:55 [PATCH v3 0/2] ivshmem: update documentation, add client/server tools David Marchand
2014-08-08  8:55 ` [PATCH v3 1/2] contrib: add ivshmem client and server David Marchand
2014-08-08 14:51   ` [Qemu-devel] " Stefan Hajnoczi
2014-08-18 12:09     ` David Marchand [this message]
2014-08-10  3:57   ` Gonglei
2014-08-18 12:19     ` [Qemu-devel] " David Marchand
2014-08-08  8:55 ` [PATCH v3 2/2] docs: update ivshmem device spec David Marchand
2014-08-08  9:04   ` Claudio Fontana
2014-08-08  9:32     ` David Marchand
2014-08-08 15:02   ` [Qemu-devel] " Stefan Hajnoczi
2014-08-26  6:47     ` David Marchand
2014-08-26 11:04       ` Paolo Bonzini
2014-08-28  9:49         ` Stefan Hajnoczi
2014-09-01  9:52           ` David Marchand
2014-09-09 19:04             ` Eric Blake
2014-08-08  9:30 ` [Qemu-devel] [PATCH v3 0/2] ivshmem: update documentation, add client/server tools Gonglei (Arei)
2014-08-08  9:54   ` David Marchand
2014-08-08 10:26     ` Gonglei (Arei)

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=53F1ED06.9020408@6wind.com \
    --to=david.marchand@6wind.com \
    --cc=armbru@redhat.com \
    --cc=cam@cs.ualberta.ca \
    --cc=claudio.fontana@huawei.com \
    --cc=jani.kokkonen@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=olivier.matz@6wind.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox