linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] ARM: kprobes: big endian support
Date: Sat, 11 Jan 2014 13:28:47 +0000	[thread overview]
Message-ID: <52D1470F.6000409@codethink.co.uk> (raw)
In-Reply-To: <1389376706-30051-1-git-send-email-taras.kondratiuk@linaro.org>

On 10/01/14 17:58, Taras Kondratiuk wrote:
> Reworked initial Ben's series for big endian support [1].
> Dropped patches that are not directly related to kprobes.
> Current set of patches is enough to have functional BE kprobes.
>
> One ARM kprobe test fails on Cortex-A15 boards (TC2 and Keystone2 EVM),
> while it passes on Pandaboard. The issue is not related to this series
> and already present in v3.13-rc7. I'll try to look into it later.

Thankyou for sorting this out, +1 for this set from me.


-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

      parent reply	other threads:[~2014-01-11 13:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 17:58 [PATCH v2 0/5] ARM: kprobes: big endian support Taras Kondratiuk
2014-01-10 17:58 ` [PATCH v2 1/5] ARM: kprobes: fix instruction fetch order with <asm/opcodes.h> Taras Kondratiuk
2014-01-10 17:58 ` [PATCH v2 2/5] ARM: kprobes-test: use <asm/opcodes.h> for instruction accesses Taras Kondratiuk
2014-01-10 17:58 ` [PATCH v2 3/5] ARM: kprobes-test: use <asm/opcodes.h> for ARM instruction building Taras Kondratiuk
2014-01-13 11:03   ` Jon Medhurst (Tixy)
2014-01-10 17:58 ` [PATCH v2 4/5] ARM: kprobes-test: use <asm/opcodes.h> for Thumb " Taras Kondratiuk
2014-01-10 17:58 ` [PATCH v2 5/5] ARM: kprobes-test: Workaround GAS .align bug Taras Kondratiuk
2014-01-11 13:28 ` Ben Dooks [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=52D1470F.6000409@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).