From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Nicolas Pitre <nico-mo2vmkxb4K0@public.gmane.org>,
Lennert Buytenhek
<buytenh-OLH4Qvv75CYX/NnBR394Jw@public.gmane.org>,
Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: ptrace(2) ARM-specific details (request for patches)
Date: Fri, 4 Nov 2016 16:59:45 +0100 [thread overview]
Message-ID: <f10daac4-4ead-5dee-2184-d35a02666006@gmail.com> (raw)
Hello Will, Catalin, (and others in the To:)
As I mentioned to you both at LPC, over time there have been
a number of ARM-specific additions to ptrace(2), and these
have not been documented yet. Would I be able to appeal to
you (and others in the To:) to send patches for these changes
(and future ptrace changes)?
The changes in question, for which I would be keen to receive
patches, are as follows:
PTRACE_GETWMMXREGS
PTRACE_SETWMMXREGS
ARM
Linux 2.6.12
PTRACE_SET_SYSCALL
ARM and ARM64
Linux 2.6.16
commit 3f471126ee53feb5e9b210ea2f525ed3bb9b7a7f
Author: Nicolas Pitre <nico-mo2vmkxb4K0@public.gmane.org>
Date: Sat Jan 14 19:30:04 2006 +0000
PTRACE_GETCRUNCHREGS
PTRACE_SETCRUNCHREGS
ARM
Linux 2.6.18
commit 3bec6ded282b331552587267d67a06ed7fd95ddd
Author: Lennert Buytenhek <buytenh-OLH4Qvv75CYX/NnBR394Jw@public.gmane.org>
Date: Tue Jun 27 22:56:18 2006 +0100
PTRACE_GETVFPREGS
PTRACE_SETVFPREGS
ARM and ARM64
Linux 2.6.30
commit 3d1228ead618b88e8606015cbabc49019981805d
Author: Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>
Date: Wed Feb 11 13:12:56 2009 +0100
PTRACE_GETHBPREGS
PTRACE_SETHBPREGS
ARM and ARM64
Linux 2.6.37
commit 864232fa1a2f8dfe003438ef0851a56722740f3e
Author: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Date: Fri Sep 3 10:42:55 2010 +0100
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2016-11-04 15:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f10daac4-4ead-5dee-2184-d35a02666006@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=buytenh-OLH4Qvv75CYX/NnBR394Jw@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nico-mo2vmkxb4K0@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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).