From: David Miller <davem@davemloft.net>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org,
linux-kernel@vger.kernel.org, roland@redhat.com
Subject: Re: [PATCH 0/5] powerpc tracehook
Date: Sun, 27 Jul 2008 00:55:18 -0700 (PDT) [thread overview]
Message-ID: <20080727.005518.08712012.davem@davemloft.net> (raw)
In-Reply-To: <1217145165.11188.132.camel@pasglop>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Sun, 27 Jul 2008 17:52:45 +1000
> On Sat, 2008-07-26 at 23:48 -0700, Roland McGrath wrote:
> > These patches are posted for review, but you can just pull the GIT branch
> > if you prefer. Patch 1/5 corrects a long-standing (minor) error in ptrace
> > behavior. The others change no existing behavior, just enable new and
> > future features to work on the arch.
>
> Hi Roland !
>
> Thanks for this. I haven't followed the story of tracehook so far, are
> those patches dependent on something else or it's all already upstream
> and do you think that's still 2.6.27 material ?
The infrastructure is in Linus's tree.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: benh@kernel.crashing.org
Cc: roland@redhat.com, linuxppc-dev@ozlabs.org, paulus@samba.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] powerpc tracehook
Date: Sun, 27 Jul 2008 00:55:18 -0700 (PDT) [thread overview]
Message-ID: <20080727.005518.08712012.davem@davemloft.net> (raw)
In-Reply-To: <1217145165.11188.132.camel@pasglop>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Sun, 27 Jul 2008 17:52:45 +1000
> On Sat, 2008-07-26 at 23:48 -0700, Roland McGrath wrote:
> > These patches are posted for review, but you can just pull the GIT branch
> > if you prefer. Patch 1/5 corrects a long-standing (minor) error in ptrace
> > behavior. The others change no existing behavior, just enable new and
> > future features to work on the arch.
>
> Hi Roland !
>
> Thanks for this. I haven't followed the story of tracehook so far, are
> those patches dependent on something else or it's all already upstream
> and do you think that's still 2.6.27 material ?
The infrastructure is in Linus's tree.
next prev parent reply other threads:[~2008-07-27 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 6:48 [PATCH 0/5] powerpc tracehook Roland McGrath
2008-07-27 6:49 ` [PATCH 1/5] powerpc: tracehook_signal_handler Roland McGrath
2008-07-27 6:51 ` [PATCH 2/5] powerpc: tracehook syscall Roland McGrath
2008-07-27 6:51 ` [PATCH 3/5] powerpc: tracehook: asm/syscall.h Roland McGrath
2008-07-27 6:52 ` [PATCH 4/5] powerpc: tracehook: TIF_NOTIFY_RESUME Roland McGrath
2008-07-27 6:53 ` [PATCH 5/5] powerpc: tracehook: CONFIG_HAVE_ARCH_TRACEHOOK Roland McGrath
2008-07-27 7:52 ` [PATCH 0/5] powerpc tracehook Benjamin Herrenschmidt
2008-07-27 7:52 ` Benjamin Herrenschmidt
2008-07-27 7:55 ` David Miller [this message]
2008-07-27 7:55 ` David Miller
2008-07-27 8:51 ` Benjamin Herrenschmidt
2008-07-27 8:51 ` Benjamin Herrenschmidt
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=20080727.005518.08712012.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.