From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: fyi - kprobes testing patches
Date: Thu, 25 Jul 2013 22:08:53 +0100 [thread overview]
Message-ID: <1374786537-10726-1-git-send-email-ben.dooks@codethink.co.uk> (raw)
I've been working on kprobes and the kprobes-test driver. It seems
there are more issues with the kprobes-test that need looking in to
so I am putting this series out to see if anyone has any comments
next reply other threads:[~2013-07-25 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 21:08 Ben Dooks [this message]
2013-07-25 21:08 ` [PATCH 1/4] ARM: kprobes: fix instruction fetch order with <asm/opcodes.h> Ben Dooks
2013-07-29 8:01 ` Jon Medhurst (Tixy)
2013-07-31 19:43 ` Ben Dooks
2013-08-02 13:57 ` Dave Martin
2013-08-02 13:58 ` Ben Dooks
2013-08-02 14:03 ` Dave Martin
2013-07-25 21:08 ` [PATCH 2/4] ARM: kprobes, change arm test to .instr Ben Dooks
2013-07-25 21:08 ` [PATCH 3/4] ARM: kprobes-test: use <asm/opcodes.h> Ben Dooks
2013-07-29 8:07 ` Jon Medhurst (Tixy)
2013-07-31 19:38 ` Ben Dooks
2013-07-25 21:08 ` [PATCH 4/4] ARM: kprobes-test: move to using a pointer to the title text Ben Dooks
2013-07-26 14:02 ` Dave Martin
2013-07-26 14:08 ` Ben Dooks
2013-07-26 10:52 ` fyi - kprobes testing patches Ben Dooks
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=1374786537-10726-1-git-send-email-ben.dooks@codethink.co.uk \
--to=ben.dooks@codethink.co.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).