From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] syscall_trace fixes and cleanups
Date: Sat, 9 Jun 2012 13:38:34 +0100 [thread overview]
Message-ID: <20120609123834.GA11168@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1339168341-29850-1-git-send-email-will.deacon@arm.com>
On Fri, Jun 08, 2012 at 04:12:17PM +0100, Will Deacon wrote:
> Hello,
>
> This is version 2 of the patches originally posted here:
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2012-May/097748.html
>
> The only changes are that (a) two of the original patches (fixes) have
> been now been merged into mainline and (b) the remaining patches in the
> series are now rebased onto -rc1, which includes Al's work on the signal
> handling / syscall restarting path.
>
> All comments welcome,
It may be a good idea to Cc Al on these.
next prev parent reply other threads:[~2012-06-09 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 15:12 [PATCH v2 0/4] syscall_trace fixes and cleanups Will Deacon
2012-06-08 15:12 ` [PATCH v2 1/4] audit: arm: only allow syscall auditing for pure EABI userspace Will Deacon
2012-06-08 15:12 ` [PATCH v2 2/4] ARM: entry: don't bother with syscall tracing on ret_from_fork path Will Deacon
2012-06-08 15:12 ` [PATCH v2 3/4] ARM: audit: move syscall auditing until after ptrace SIGTRAP handling Will Deacon
2012-06-08 15:12 ` [PATCH v2 4/4] ARM: ptrace: provide separate functions for tracing syscall {entry, exit} Will Deacon
2012-06-09 12:38 ` Russell King - ARM Linux [this message]
2012-06-12 21:15 ` [PATCH v2 0/4] syscall_trace fixes and cleanups Will Deacon
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=20120609123834.GA11168@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).