From: Catalin Marinas <catalin.marinas@arm.com>
To: Claudio Scordino <claudio@evidence.eu.com>
Cc: linux-kernel@vger.kernel.org, rmk+kernel@arm.linux.org.uk,
akpm@linux-foundation.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH][RE-SUBMIT] Default setting of the ARM_UNWIND option
Date: Fri, 30 Oct 2009 12:39:16 +0000 [thread overview]
Message-ID: <1256906356.27014.22.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <4AEAC9D8.9000304@evidence.eu.com>
On Fri, 2009-10-30 at 12:11 +0100, Claudio Scordino wrote:
> From: Claudio Scordino <claudio@evidence.eu.com>
> Date: Fri, 30 Oct 2009 11:46:00 +0100
> Subject: [PATCH 1/1] ARM unwind is known to compile only with EABI and
> not-buggy compilers.
>
> ARM unwind is known to compile only with EABI and not-buggy compilers.
> The problem is not the unwinding information but the
> -fno-frame-pointer option added as a result of !CONFIG_FRAME_POINTER.
> Now we check the compiler and raise a #warning in case of wrong
> compiler.
>
>
> Signed-off-by: Claudio Scordino <claudio@evidence.eu.com>
Unless others have objections, here's my ack:
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
--
Catalin
prev parent reply other threads:[~2009-10-30 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AD73DA4.4050006@evidence.eu.com>
[not found] ` <1255620333.10164.77.camel@pc1117.cambridge.arm.com>
2009-10-19 10:15 ` [PATCH] " Claudio Scordino
2009-10-19 10:16 ` Claudio Scordino
2009-10-26 8:27 ` [PATCH][RE-SUBMIT] " Claudio Scordino
2009-10-26 11:10 ` Catalin Marinas
2009-10-28 11:37 ` Claudio Scordino
2009-10-28 11:37 ` Claudio Scordino
2009-10-28 14:58 ` Catalin Marinas
2009-10-30 11:11 ` Claudio Scordino
2009-10-30 12:39 ` Catalin Marinas [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=1256906356.27014.22.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=claudio@evidence.eu.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®