qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Kirill Shutemov <k.shutemov@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] Simplily linux-user/path.c
Date: Thu, 21 Dec 2006 14:48:51 +0000	[thread overview]
Message-ID: <200612211448.52161.paul@codesourcery.com> (raw)
In-Reply-To: <1d592d70612120456s21299325q811e75310d432266@mail.gmail.com>

On Tuesday 12 December 2006 12:56, Kirill Shutemov wrote:
> I have no ideas why path.c is so complex. Any? In the attachment
> rewritten version. It has tested with qemu-arm.

Your patch is buggy. You're returning a pointer to a stack allocated object.

Paul

      parent reply	other threads:[~2006-12-21 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12  1:45 [Qemu-devel] [PATCH] Simplily linux-user/path.c Kirill Shutemov
2006-12-12 12:56 ` Kirill Shutemov
2006-12-13 17:50   ` [Qemu-devel] " Kirill Shutemov
2006-12-21 14:48   ` Paul Brook [this message]

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=200612211448.52161.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=k.shutemov@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).