From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] syscall_trace fixes and cleanups
Date: Tue, 12 Jun 2012 22:15:10 +0100 [thread overview]
Message-ID: <20120612211510.GA24380@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20120609123834.GA11168@n2100.arm.linux.org.uk>
Hi Russell,
On Sat, Jun 09, 2012 at 01:38:34PM +0100, Russell King - ARM Linux wrote:
> On Fri, Jun 08, 2012 at 04:12:17PM +0100, Will Deacon wrote:
> > 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.
Sure. Since I've not received any other comments on this series, I'll
repost this week with Al on CC.
Will
prev parent reply other threads:[~2012-06-12 21:15 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 ` [PATCH v2 0/4] syscall_trace fixes and cleanups Russell King - ARM Linux
2012-06-12 21:15 ` Will Deacon [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=20120612211510.GA24380@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--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).