From: Avi Kivity <avi@qumranet.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: kvm-devel@lists.sourceforge.net,
kvm-ppc-devel@lists.sourceforge.net,
Jerone Young <jyoung5@us.ibm.com>,
hollisb@us.ibm.com
Subject: Re: [kvm-ppc-devel] [kvm-devel] [PATCH 1 of 4] Add "make sync" to
Date: Mon, 14 Apr 2008 12:04:45 +0000 [thread overview]
Message-ID: <4803485D.6030605@qumranet.com> (raw)
In-Reply-To: <20080414115403.GA27703@infradead.org>
Christoph Hellwig wrote:
> It would be nice to just be able to build kvm from git without a kernel
> around. The lack of that is what in fact keeps from hacking kvm
> userspace currently.
>
It would be nice, but committing all header changes twice is not so nice
and error prone as well.
Anyone serious about hacking kvm-userspace would not be deterred by the
additional clone.
[maybe we can provide an automatically-generated git tree that has only
the kernel headers?]
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: kvm-devel@lists.sourceforge.net,
kvm-ppc-devel@lists.sourceforge.net,
Jerone Young <jyoung5@us.ibm.com>,
hollisb@us.ibm.com
Subject: Re: [PATCH 1 of 4] Add "make sync" to sync need kernel headers to kvm-userspace
Date: Mon, 14 Apr 2008 15:04:45 +0300 [thread overview]
Message-ID: <4803485D.6030605@qumranet.com> (raw)
In-Reply-To: <20080414115403.GA27703@infradead.org>
Christoph Hellwig wrote:
> It would be nice to just be able to build kvm from git without a kernel
> around. The lack of that is what in fact keeps from hacking kvm
> userspace currently.
>
It would be nice, but committing all header changes twice is not so nice
and error prone as well.
Anyone serious about hacking kvm-userspace would not be deterred by the
additional clone.
[maybe we can provide an automatically-generated git tree that has only
the kernel headers?]
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-14 12:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 8:37 [PATCH 0 of 4] Sync kernel headers to kvm-userspace Jerone Young
2008-04-14 8:37 ` [PATCH 1 of 4] Add "make sync" to sync need " Jerone Young
2008-04-14 8:50 ` [kvm-ppc-devel] [kvm-devel] [PATCH 1 of 4] Add "make sync" to Christoph Hellwig
2008-04-14 8:50 ` [PATCH 1 of 4] Add "make sync" to sync need kernel headers to kvm-userspace Christoph Hellwig
2008-04-14 11:47 ` [kvm-ppc-devel] [kvm-devel] [PATCH 1 of 4] Add "make sync" to Avi Kivity
2008-04-14 11:47 ` [PATCH 1 of 4] Add "make sync" to sync need kernel headers to kvm-userspace Avi Kivity
2008-04-14 11:54 ` [kvm-ppc-devel] [kvm-devel] [PATCH 1 of 4] Add "make sync" to Christoph Hellwig
2008-04-14 11:54 ` [PATCH 1 of 4] Add "make sync" to sync need kernel headers to kvm-userspace Christoph Hellwig
2008-04-14 12:04 ` Avi Kivity [this message]
2008-04-14 12:04 ` Avi Kivity
2008-04-14 14:23 ` [kvm-ppc-devel] [kvm-devel] [PATCH 1 of 4] Add "make sync" to Anthony Liguori
2008-04-14 14:23 ` [PATCH 1 of 4] Add "make sync" to sync need kernel headers to kvm-userspace Anthony Liguori
2008-04-14 14:43 ` [kvm-ppc-devel] [kvm-devel] [PATCH 1 of 4] Add "make sync" to Avi Kivity
2008-04-14 14:43 ` [PATCH 1 of 4] Add "make sync" to sync need kernel headers to kvm-userspace Avi Kivity
2008-04-14 14:20 ` [kvm-ppc-devel] [kvm-devel] [PATCH 1 of 4] Add "make sync" to Anthony Liguori
2008-04-14 14:20 ` [PATCH 1 of 4] Add "make sync" to sync need kernel headers to kvm-userspace Anthony Liguori
2008-04-14 14:18 ` [kvm-ppc-devel] [kvm-devel] [PATCH 1 of 4] Add "make sync" to Anthony Liguori
2008-04-14 14:18 ` [PATCH 1 of 4] Add "make sync" to sync need kernel headers to kvm-userspace Anthony Liguori
2008-04-15 7:29 ` [kvm-ppc-devel] [kvm-devel] [PATCH 1 of 4] Add "make sync" to Avi Kivity
2008-04-15 7:29 ` [PATCH 1 of 4] Add "make sync" to sync need kernel headers to kvm-userspace Avi Kivity
2008-04-14 8:37 ` [PATCH 2 of 4] Fix libfdt to include synced headers Jerone Young
2008-04-14 8:37 ` [PATCH 3 of 4] Fix user to include synced headers & remove kerneldir option Jerone Young
2008-04-14 8:37 ` [PATCH 4 of 4] Remove kvm kernel-path option from qemu Jerone Young
2008-04-15 8:38 ` [kvm-ppc-devel] [kvm-devel] [PATCH 4 of 4] Remove kvm Avi Kivity
2008-04-15 8:38 ` [PATCH 4 of 4] Remove kvm kernel-path option from qemu Avi Kivity
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=4803485D.6030605@qumranet.com \
--to=avi@qumranet.com \
--cc=hch@infradead.org \
--cc=hollisb@us.ibm.com \
--cc=jyoung5@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=kvm-ppc-devel@lists.sourceforge.net \
/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.