public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Roland McGrath <roland@redhat.com>
Cc: Chris Zankel <chris@zankel.net>,
	David Howells <dhowells@redhat.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Greg Ungerer <gerg@uclinux.org>,
	Haavard Skinnemoen <hskinnemoen@atmel.com>,
	Helge Deller <deller@gmx.de>,
	Hirokazu Takata <takata@linux-m32r.org>,
	Jeff Dike <jdike@addtoit.com>, Kyle McMartin <kyle@mcmartin.ca>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Mike Frysinger <vapier.adi@gmail.com>,
	Paul Mundt <lethal@linux-sh.org>,
	Roman Zippel <zippel@linux-m68k.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] ptrace: remove PT_DTRACE from arch/* except arch/um
Date: Thu, 23 Apr 2009 21:31:53 +0200	[thread overview]
Message-ID: <20090423193153.GA14869@redhat.com> (raw)

As Roland pointed out, PT_DTRACE is not actually used except in
uml and should die.

Remove it from h8300, avr32, mn10300, parisc, s390, sh, xtensa, m68k,
m68knommu, m32r. The patches are rather simple (but untested), I tried
to split the changes by "category".

With this series arch/um is the only one who uses PT_DTRACE and thinks
task_lock() is needed for ptrace related code. This will be addressed
later (tanks Jeff for your reply).

Oleg.


             reply	other threads:[~2009-04-23 19:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 19:31 Oleg Nesterov [this message]
2009-04-23 23:22 ` [PATCH 0/4] ptrace: remove PT_DTRACE from arch/* except arch/um 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=20090423193153.GA14869@redhat.com \
    --to=oleg@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris@zankel.net \
    --cc=deller@gmx.de \
    --cc=dhowells@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=hskinnemoen@atmel.com \
    --cc=jdike@addtoit.com \
    --cc=kyle@mcmartin.ca \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=takata@linux-m32r.org \
    --cc=vapier.adi@gmail.com \
    --cc=ysato@users.sourceforge.jp \
    --cc=zippel@linux-m68k.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