From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v19 00/11] ARM: kprobes: OPTPROBES and other improvements.
Date: Wed, 07 Jan 2015 13:40:14 +0000 [thread overview]
Message-ID: <1420638014.4044.52.camel@linaro.org> (raw)
In-Reply-To: <1420457284-76923-1-git-send-email-wangnan0@huawei.com>
I think that the patches up to 09/11 inclusive have been though more
that enough review and revisions to think about getting them merged,
there doesn't seem much point in continuously resending them whilst new
features are built on top of them.
Masami Hiramatsu, are you happy for your patch to generic+X86 kprobes
code [1] to go through the ARM maintainers tree, assuming Russell is
also happy with that. Or should that go via a different route?
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/313218.html
Wang Nan, assuming everyone is happy, can you put together a branch in a
git repository for those patches, or I'm more than happy to do that if
you like. Then I can give the series a final test and we can send a pull
request to Russell King.
Thanks all
--
Tixy
next prev parent reply other threads:[~2015-01-07 13:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 11:28 [PATCH v19 00/11] ARM: kprobes: OPTPROBES and other improvements Wang Nan
2015-01-05 11:29 ` [PATCH v19 01/11] ARM: probes: move all probe code to dedicate directory Wang Nan
2015-01-09 2:19 ` [PATCH v20 " Wang Nan
2015-01-09 9:47 ` Jon Medhurst (Tixy)
2015-01-09 9:50 ` Wang Nan
2015-01-09 2:28 ` [PATCH v19 " Wang Nan
2015-01-05 11:29 ` [PATCH v19 02/11] ARM: kprobes: remove unused ARM decoder actions Wang Nan
2015-01-07 11:50 ` Jon Medhurst (Tixy)
2015-01-05 11:29 ` [PATCH v19 03/11] ARM: kprobes: introduces checker Wang Nan
2015-01-05 11:29 ` [PATCH v19 04/11] ARM: kprobes: collects stack consumption for store instructions Wang Nan
2015-01-05 11:29 ` [PATCH v19 05/11] ARM: kprobes: disallow probing stack consuming instructions Wang Nan
2015-01-05 11:29 ` [PATCH v19 06/11] ARM: kprobes: Add test cases for " Wang Nan
2015-01-05 11:29 ` [PATCH v19 07/11] kprobes: Pass the original kprobe for preparing optimized kprobe Wang Nan
2015-01-05 11:29 ` [PATCH v19 08/11] ARM: kprobes: enable OPTPROBES for ARM 32 Wang Nan
2015-01-07 13:01 ` Jon Medhurst (Tixy)
2015-01-09 6:37 ` [PATCH v20 " Wang Nan
2015-01-09 10:25 ` Jon Medhurst (Tixy)
2015-01-09 10:55 ` Wang Nan
2015-01-09 16:35 ` Russell King - ARM Linux
2015-01-09 17:28 ` Jon Medhurst (Tixy)
2015-01-09 17:57 ` Russell King - ARM Linux
2015-01-09 19:18 ` Jon Medhurst (Tixy)
2015-01-09 6:51 ` [PATCH v19 " Wang Nan
2015-01-05 11:29 ` [PATCH v19 09/11] ARM: kprobes: Fix unreliable MRS instruction tests Wang Nan
2015-01-05 11:29 ` [PATCH v19 10/11] ARM: kprobes: check register usage for probed instruction Wang Nan
2015-01-13 15:01 ` Jon Medhurst (Tixy)
2015-01-13 16:13 ` [PATCH] " Jon Medhurst (Tixy)
2015-01-19 10:37 ` Wang Nan
2015-01-05 11:34 ` [PATCH v19 11/11] ARM: optprobes: execute instruction during restoring if possible Wang Nan
2015-01-07 13:40 ` Jon Medhurst (Tixy) [this message]
2015-01-20 2:17 ` [PATCH v19 00/11] ARM: kprobes: OPTPROBES and other improvements Masami Hiramatsu
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=1420638014.4044.52.camel@linaro.org \
--to=tixy@linaro.org \
--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).