From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix 64 bit issue in slirp
Date: Mon, 12 Jan 2009 18:05:20 +0200 [thread overview]
Message-ID: <f43fc5580901120805g23d535a1pabb059cf7f9571ed@mail.gmail.com> (raw)
In-Reply-To: <20090112150643.GP3267@redhat.com>
On 1/12/09, Gleb Natapov <gleb@redhat.com> wrote:
> On Mon, Jan 12, 2009 at 04:54:44PM +0200, Blue Swirl wrote:
> > On 1/12/09, Gleb Natapov <gleb@redhat.com> wrote:
> > >
> > > Signed-off-by: Gleb Natapov <gleb@redhat.com>
> >
> > Great, but did you really fix all pointer accesses, including the port
> > number stuff?
> >
>
> All that I found obviously :) And yes the one you are talking about is
> fixed. Look at "struct mbuf_ptr"
Excellent! The patch passes my tests. I'll apply it unless there are objections.
This also means that we can finally get rid of the last warnings.
next prev parent reply other threads:[~2009-01-12 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 14:28 [Qemu-devel] [PATCH] fix 64 bit issue in slirp Gleb Natapov
2009-01-12 14:40 ` Gleb Natapov
2009-01-12 14:54 ` Blue Swirl
2009-01-12 15:06 ` Gleb Natapov
2009-01-12 16:05 ` Blue Swirl [this message]
2009-01-12 19:30 ` malc
2009-01-13 20:00 ` Blue Swirl
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=f43fc5580901120805g23d535a1pabb059cf7f9571ed@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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).