From: David Howells <dhowells@redhat.com>
To: bryan.wu@analog.com
Cc: roland@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] utrace: nommu fixup support utrace
Date: Tue, 06 Mar 2007 09:37:38 +0000 [thread overview]
Message-ID: <17048.1173173858@redhat.com> (raw)
In-Reply-To: <1173165927.17134.5.camel@roc-desktop>
Wu, Bryan <bryan.wu@analog.com> wrote:
> When adding utrace support to blackfin architecture, I found a compiling
> error in nommu related utrace stuff. Then this little patch will fix
> this for nommu arch utrace.
You really don't want to do it like this. This prevents ELF shared libraries
from being shared at all if UTRACE is enabled.
David
next prev parent reply other threads:[~2007-03-06 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 7:25 [PATCH -mm] utrace: nommu fixup support utrace Wu, Bryan
2007-03-06 9:37 ` David Howells [this message]
2007-03-06 9:49 ` Wu, Bryan
2007-03-07 3:42 ` Roland McGrath
2007-03-07 11:10 ` David Howells
2007-03-09 7:37 ` Roland McGrath
2007-03-09 11:41 ` David Howells
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=17048.1173173858@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.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