public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Roland McGrath <roland@redhat.com>
Cc: linux-arch@vger.kernel.org, utrace-devel@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: CONFIG_HAVE_ARCH_TRACEHOOK and you
Date: Fri, 12 Sep 2008 04:23:01 -0400	[thread overview]
Message-ID: <20080912082301.GA28385@infradead.org> (raw)
In-Reply-To: <20080912025733.E55F415420D@magilla.localdomain>

On Thu, Sep 11, 2008 at 07:57:33PM -0700, Roland McGrath wrote:
>     3. arch_ptrace()
> 
>           * You must define arch_ptrace() and not #define __ARCH_SYS_PTRACE.

__ARCH_SYS_PTRACE is already gone :)

> 
>     4. compat_arch_ptrace()
> 
>           * If your arch uses CONFIG_COMPAT, you must define
>             compat_arch_ptrace() and #define __ARCH_WANT_COMPAT_SYS_PTRACE.

This should be gone for 2.6.28, too.  (no ACK from the ia64 people yet,
but mips and parisc are doen for sure)

  parent reply	other threads:[~2008-09-12  8:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12  2:57 CONFIG_HAVE_ARCH_TRACEHOOK and you Roland McGrath
2008-09-12  2:57 ` Roland McGrath
2008-09-12  8:23 ` Christoph Hellwig [this message]
2008-09-12 13:05 ` Paul Mundt
2008-09-15 20:38   ` Roland McGrath
2008-09-12 13:13 ` Russell King
2008-09-12 21:57   ` David Miller
2008-09-12 22:31   ` Roland McGrath
2008-09-12 22:31     ` Roland McGrath
2008-09-12 22:37     ` David Miller
2008-09-12 22:39       ` Roland McGrath
2008-09-12 22:39         ` Roland McGrath
2008-09-12 22:40         ` David Miller
2008-09-12 22:45           ` Roland McGrath
2008-09-12 22:45             ` Roland McGrath
  -- strict thread matches above, loose matches on Subject: below --
2008-09-12 13:40 Russell King
2008-09-12 13:40 ` Russell King
2008-09-12 23:57 ` Roland McGrath
2008-09-12 23:57   ` Roland McGrath

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=20080912082301.GA28385@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=utrace-devel@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