From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] powerpc, ptrace: Add few more ptrace request macros
Date: Wed, 02 Apr 2014 09:10:21 +0530 [thread overview]
Message-ID: <533B86A5.90700@linux.vnet.ibm.com> (raw)
In-Reply-To: <25834.1396399387@ale.ozlabs.ibm.com>
On 04/02/2014 06:13 AM, Michael Neuling wrote:
> Anshuman Khandual <khandual@linux.vnet.ibm.com> wrote:
>> > This patch adds few more ptrace request macros expanding
>> > the existing capability. These ptrace requests macros can
>> > be classified into two categories.
> Why is this only an RFC?
>
Looking for comments, suggestions, concerns from people. But looks
like its bit big a patch to review at once.
> Also, please share the test case that you wrote for this.
Will split the patch into multiple components, add the test case
and send out again.
prev parent reply other threads:[~2014-04-02 3:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 11:14 [RFC] powerpc, ptrace: Add few more ptrace request macros Anshuman Khandual
2014-04-02 0:43 ` Michael Neuling
2014-04-02 3:40 ` Anshuman Khandual [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=533B86A5.90700@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.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;
as well as URLs for NNTP newsgroup(s).