From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] ARM: kprobes-test: use <asm/opcodes.h> for instruction accesses
Date: Thu, 09 Jan 2014 11:04:51 +0000 [thread overview]
Message-ID: <1389265491.4041.6.camel@linaro1.home> (raw)
In-Reply-To: <CAArO44ump6fid28qDGYK3=vMNLpgicMjYNO1hOdyU7D-Lkd3bQ@mail.gmail.com>
On Thu, 2014-01-09 at 12:54 +0200, Taras Kondratiuk wrote:
> On 3 January 2014 17:53, Jon Medhurst (Tixy) <tixy@linaro.org> wrote:
> > On Mon, 2013-12-23 at 18:19 +0200, Taras Kondratiuk wrote:
> >> From: Ben Dooks <ben.dooks@codethink.co.uk>
> >>
> >> Ensure we read instructions in the correct endian-ness by using
> >> the <asm/opcodes.h> helper to transform them as necessary.
> >>
> >> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> >> [taras.kondratiuk at linaro.org: fix next_instruction() function]
> >> Signed-off-by: Taras Kondratiuk <taras.kondratiuk@linaro.org>
> >> ---
> >
> > Apart from the spurious line removal (see below) then:
> >
> > Acked-by: Jon Medhurst <tixy@linaro.org>
> >
> > and you can include an ACK for the other patches in this series too.
> >
> > Thanks.
>
> >> @@ -1593,7 +1594,6 @@ static int run_test_cases(void (*tests)(void), const union decode_item *table)
> >> return 0;
> >> }
> >>
> >> -
> >
> > I know the above blank line isn't needed but I believe the convention is
> > to avoid doing unrelated white-space clean-ups in patches.
>
> Right, I will remove it.
> Should this series go through Russell's patch tracking system or it
> can be pulled
> to some tree?
I would assume as a pull request sent to Russell using the email alias
he uses for these things: linux+pull at arm.linux.org.uk I'm sure he's
shout up if I'm wrong...
--
Tixy
next prev parent reply other threads:[~2014-01-09 11:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 16:19 [PATCH 0/5] ARM: kprobes: big endian support Taras Kondratiuk
2013-12-23 16:19 ` [PATCH 1/5] ARM: kprobes: fix instruction fetch order with <asm/opcodes.h> Taras Kondratiuk
2013-12-23 16:19 ` [PATCH 2/5] ARM: kprobes-test: use <asm/opcodes.h> for instruction accesses Taras Kondratiuk
2014-01-03 15:53 ` Jon Medhurst (Tixy)
2014-01-09 10:54 ` Taras Kondratiuk
2014-01-09 11:04 ` Jon Medhurst (Tixy) [this message]
2014-01-09 12:00 ` Taras Kondratiuk
2013-12-23 16:19 ` [PATCH 3/5] ARM: kprobes-test: use <asm/opcodes.h> for ARM instruction building Taras Kondratiuk
2014-01-10 15:49 ` Taras Kondratiuk
2013-12-23 16:19 ` [PATCH 4/5] ARM: kprobes-test: use <asm/opcodes.h> for Thumb " Taras Kondratiuk
2013-12-23 16:19 ` [PATCH 5/5] ARM: kprobes-test: Workaround GAS .align bug Taras Kondratiuk
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=1389265491.4041.6.camel@linaro1.home \
--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