From: Ralf Baechle <ralf@linux-mips.org>
To: Tony Wu <tung7970@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH v3 1/2] MIPS: fix sibling call handling in get_frame_info
Date: Sat, 18 May 2013 01:56:08 +0200 [thread overview]
Message-ID: <20130517235608.GB24568@linux-mips.org> (raw)
In-Reply-To: <20130512160429.GA982@hades>
On Mon, May 13, 2013 at 12:04:29AM +0800, Tony Wu wrote:
> Date: Mon, 13 May 2013 00:04:29 +0800
> From: Tony Wu <tung7970@gmail.com>
> To: ralf@linux-mips.org, linux-mips@linux-mips.org
> Subject: [PATCH v3 1/2] MIPS: fix sibling call handling in get_frame_info
> Content-Type: text/plain; charset=us-ascii
I've applied both your patches but both did apply with fuzz so you may
want to verify everything is working fine.
Thanks,
Ralf
prev parent reply other threads:[~2013-05-17 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 16:04 [PATCH v3 1/2] MIPS: fix sibling call handling in get_frame_info Tony Wu
2013-05-17 23:56 ` Ralf Baechle [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=20130517235608.GB24568@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=tung7970@gmail.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