public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Yufeng Zhang <Yufeng.Zhang@arm.com>
Cc: libffi-discuss@sourceware.org
Subject: Re: [PATCH, AArch64] Fix Call Frame Information in ffi_closure_SYSV
Date: Mon, 06 Jan 2014 12:36:00 -0000	[thread overview]
Message-ID: <CAFqB+PxptfxcaEko-c3EgOZ7HBpneCriSRaMDbEre9Ht0H9c3Q@mail.gmail.com> (raw)
In-Reply-To: <52B8815B.5030700@arm.com>

On 23 December 2013 18:30, Yufeng Zhang <Yufeng.Zhang@arm.com> wrote:
> Hi,
>
> This patch fixes a bug in ./src/aarch64/sysv.S:ffi_closure_SYSV where stack
> unwinding information was not generated correctly.
>
> OK for the mainline?

This patch looks reasonable to me.

/Marcus

  reply	other threads:[~2014-01-06 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23 18:30 Yufeng Zhang
2014-01-06 12:36 ` Marcus Shawcroft [this message]
2014-01-14 12:10 ` [PING] " Yufeng Zhang
2014-02-12 18:08   ` [PING^2] " Yufeng Zhang
2014-02-20 14:59     ` [PING^3] " Yufeng Zhang
2014-02-28  5:28   ` [PING] " Anthony Green

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=CAFqB+PxptfxcaEko-c3EgOZ7HBpneCriSRaMDbEre9Ht0H9c3Q@mail.gmail.com \
    --to=marcus.shawcroft@gmail.com \
    --cc=Yufeng.Zhang@arm.com \
    --cc=libffi-discuss@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).