From: Scott Pakin <pakin@lanl.gov>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org,
kvm-ia64-devel@lists.sourceforge.net
Subject: [Qemu-devel] Re: [kvm-devel] [PATCH] Making SLIRP code more 64-bit clean
Date: Thu, 31 Jan 2008 11:38:26 -0700 [thread overview]
Message-ID: <47A215A2.4070407@lanl.gov> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDCD31F4E@pdsmsx415.ccr.corp.intel.com>
Zhang, Xiantao wrote:
> Unfortunately, it can's apply on tip. Could you attach the diff ?
It works for me:
$ git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-userspace.git
remote: Generating pack...
remote: Done counting 37449 objects.
remote: Deltifying 37449 objects...
remote: 100% (37449/37449) done
Indexing 37449 objects.
remote: Total 37449 (delta 24712), reused 37189 (delta 24506)
100% (37449/37449) done
Resolving 24712 deltas.
100% (24712/24712) done
Checking files out...
100% (948/948) done
$ cd kvm-userspace
$ patch -p1 < ~/tcp_int32_pointer_cast.patch
patching file qemu/exec-all.h
patching file qemu/slirp/ip.h
patching file qemu/slirp/misc.c
patching file qemu/slirp/slirp.h
patching file qemu/slirp/tcp_var.h
$
-- Scott
next prev parent reply other threads:[~2008-01-31 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 17:11 [Qemu-devel] [PATCH] Making SLIRP code more 64-bit clean Scott Pakin
2008-01-30 4:27 ` [Qemu-devel] RE: [kvm-devel] " Zhang, Xiantao
2008-01-30 16:42 ` [Qemu-devel] " Scott Pakin
2008-01-30 17:10 ` Blue Swirl
2008-02-01 1:26 ` [kvm-ia64-devel] [Qemu-devel] Re: [kvm-devel] [PATCH] MakingSLIRP " Zhang, Xiantao
2008-01-31 8:24 ` [Qemu-devel] RE: [kvm-devel] [PATCH] Making SLIRP " Zhang, Xiantao
2008-01-31 18:38 ` Scott Pakin [this message]
2008-02-01 1:37 ` [Qemu-devel] " Scott Pakin
2008-02-01 2:44 ` [Qemu-devel] RE: [kvm-ia64-devel] [kvm-devel] [PATCH] Making SLIRP code more64-bit clean Zhang, Xiantao
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=47A215A2.4070407@lanl.gov \
--to=pakin@lanl.gov \
--cc=kvm-devel@lists.sourceforge.net \
--cc=kvm-ia64-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
--cc=xiantao.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).