All of lore.kernel.org
 help / color / mirror / Atom feed
From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] ARM: probes: big-endian support
Date: Tue, 01 Apr 2014 15:22:52 +0100	[thread overview]
Message-ID: <533ACBBC.2080907@codethink.co.uk> (raw)
In-Reply-To: <533AC981.6070101@linaro.org>

On 01/04/14 15:13, Taras Kondratiuk wrote:
> Hi Russell,
>
> Please pull fixes for ARM kprobes/uprobes big-endian support.
>
> It is reworked initial Ben's series for big endian support [1].
> Dropped patches that are not directly related to probes and rebased
> series on top of Dave Long's ARM uprobes series. Current set of
> patches is enough to have functional BE kprobes and uprobes.
>
> 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 since v3.13-rc7.

Thanks for sorting this out.

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

      reply	other threads:[~2014-04-01 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 14:13 [GIT PULL v2] ARM: probes: big-endian support Taras Kondratiuk
2014-04-01 14:22 ` 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=533ACBBC.2080907@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.