From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: "Andrew Morton" <akpm@osdl.org>,
davej@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: CONFIG_UNWIND_INFO
Date: Wed, 8 Feb 2006 17:28:22 +0100 [thread overview]
Message-ID: <200602081728.22726.ak@suse.de> (raw)
In-Reply-To: <43EA268A.76F0.0078.0@novell.com>
On Wednesday 08 February 2006 17:12, Jan Beulich wrote:
> Attached an updated patch, disallowing the option for all architectures that have been determined to potentially have
> problems with the resulting relocations. Jan
Looks good to me.
-Andi
prev parent reply other threads:[~2006-02-08 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43E0719F020000780000FAF6@emea1-mh.id2.novell.com>
[not found] ` <20060201005324.2c19d78c.akpm@osdl.org>
2006-02-08 16:12 ` CONFIG_UNWIND_INFO Jan Beulich
2006-02-08 16:28 ` Andi Kleen [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=200602081728.22726.ak@suse.de \
--to=ak@suse.de \
--cc=JBeulich@novell.com \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.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